CVE-2024-38599

/// Technical description

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 wrong place at 0x0000b050(2)

jffs2: nextblock 0x0000a000, expected at 0000b00c

jffs2: error: (823) do_verify_xattr_datum: node CRC failed at 0x01e050,

read=0xfc892c93, calc=0x000000

jffs2: notice: (823) jffs2_get_inode_nodes: Node header CRC failed

at 0x01e00c. {848f,2fc4,0fef511f,59a3d171}

jffs2: Node at 0x0000000c with length 0x00001044 would run over the

end of the erase block

jffs2: Perhaps the

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References