CVE-2024-38599 remediation guide

Linux Linux, SIMATIC S7-1500 TM MFP - GNU/Linux subsystem, linux kernel

In the Linux kernel, the following vulnerability has been resolved: jffs2: prevent xattr node from overflowing the eraseblock Add a check to make sure that the requested xattr node size is no larger than the eraseblock minus the cleanmarker. Unlike the usual inode nodes, the xattr nodes aren't split into parts and spread across multiple eraseblocks, which means that a xattr node must not occupy more than one eraseblock. If the requested xattr value is too large, the xattr node can spill onto the next eraseblock, overwriting the nodes and causing errors such as: jffs2: argh. node added in wr...

Open CVE record

ProductLinux Linux, SIMATIC S7-1500 TM MFP - GNU/Linux subsystem, linux kernel

Affected versions>= aa98d7cf59b5b0764d3502662053489585faf2fe < 2904e1d9b64f72d291095e3cbb31634f08788b11, >= aa98d7cf59b5b0764d3502662053489585faf2fe < 526235dffcac74c7823ed504dfac4f88d84ba5df, >= aa98d7cf59b5b0764d3502662053489585faf2fe < f0eea095ce8c959b86e1e57fe36ca4fea5ae54f8, >= aa98d7cf59b5b0764d3502662053489585faf2fe < a1d21bcd78cf4a4353e1e835789429c6b76aca8b, >= aa98d7cf59b5b0764d3502662053489585faf2fe < f06969df2e40ab1dc8f4364a5de967830c74a098, >= aa98d7cf59b5b0764d3502662053489585faf2fe < af82d8d2179b7277ad627c39e7e0778f1c86ccdb, >= aa98d7cf59b5b0764d3502662053489585faf2fe < 8d431391320c5c5398ff966fb3a95e68a7def275, >= aa98d7cf59b5b0764d3502662053489585faf2fe < 978a12c91b38bf1a213e567f3c20e2beef215f07, >= aa98d7cf59b5b0764d3502662053489585faf2fe < c6854e5a267c28300ff045480b5a7ee7f6f1d913, >= 2.6.18, >= 2.6.18 < 4.19.316, >= 4.20 < 5.4.278, >= 5.5 < 5.10.219, >= 5.11 < 5.15.161, >= 5.16 < 6.1.93, >= 6.2 < 6.6.33, >= 6.7 < 6.8.12, >= 6.9 < 6.9.3

Fixed versions4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93, 6.6.33, 6.8.12, 6.9.3

Priority basisReview · CVSS 7.1 · EPSS 0.24%

Identify the affected asset

Confirm whether Linux Linux, SIMATIC S7-1500 TM MFP - GNU/Linux subsystem, linux kernel is installed, record the deployed version and installation path, and identify exposed interfaces.

Record the product name, package or appliance identifier, and installed version.
Identify internet-facing, administrative, API, and internal access paths.
Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: >= aa98d7cf59b5b0764d3502662053489585faf2fe < 2904e1d9b64f72d291095e3cbb31634f08788b11, >= aa98d7cf59b5b0764d3502662053489585faf2fe < 526235dffcac74c7823ed504dfac4f88d84ba5df, >= aa98d7cf59b5b0764d3502662053489585faf2fe < f0eea095ce8c959b86e1e57fe36ca4fea5ae54f8, >= aa98d7cf59b5b0764d3502662053489585faf2fe < a1d21bcd78cf4a4353e1e835789429c6b76aca8b, >= aa98d7cf59b5b0764d3502662053489585faf2fe < f06969df2e40ab1dc8f4364a5de967830c74a098, >= aa98d7cf59b5b0764d3502662053489585faf2fe < af82d8d2179b7277ad627c39e7e0778f1c86ccdb, >= aa98d7cf59b5b0764d3502662053489585faf2fe < 8d431391320c5c5398ff966fb3a95e68a7def275, >= aa98d7cf59b5b0764d3502662053489585faf2fe < 978a12c91b38bf1a213e567f3c20e2beef215f07, >= aa98d7cf59b5b0764d3502662053489585faf2fe < c6854e5a267c28300ff045480b5a7ee7f6f1d913, >= 2.6.18, >= 2.6.18 < 4.19.316, >= 4.20 < 5.4.278, >= 5.5 < 5.10.219, >= 5.11 < 5.15.161, >= 5.16 < 6.1.93, >= 6.2 < 6.6.33, >= 6.7 < 6.8.12, >= 6.9 < 6.9.3. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93, 6.6.33, 6.8.12, 6.9.3. Preserve configuration and rollback material before change.

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

Confirm the expected version and package state.
Run a functional health check for critical service paths.
Review authentication, error, application, and security monitoring logs.
Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.