ubifs: fix out-of-bounds read in signature length check
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: ubifs: fix out-of-bounds read in signature length check ubifs_sb_verify_signature() bounds the on-disk ubifs_sig_node->len field before handing the signature payload to verify_pkcs7_signature(), but the check has the wrong sign: if (le32_to_cpu(signode->len) > snod->len + sizeof(struct ubifs_sig_node)) The signature bytes start sizeof(struct ubifs_sig_node) (UBIFS_SIG_NODE_SZ, 64 bytes) into the node, so the payload is at most snod->len - sizeof(struct ubifs_sig_node) bytes long. Adding the header size instead of subtracting it accepts a declared length up to 2 * UBIFS_SIG_NODE_SZ larger than the node actually holds -- past the end of c->sbuf, which is vmalloc(c->leb_size). verify_pkcs7_signature() -> pkcs7_parse_message() -> asn1_ber_decoder() is then handed that inflated length and reads beyond the allocation while walking the DER headers. The node length comes straight from the mounted image, so a crafted signed UBIFS image reaches this via ubifs_read_superblock() before the signature is cryptographically checked. snod->len is guaranteed to be >= UBIFS_SIG_NODE_SZ by the node scanner (c->ranges[UBIFS_SIG_NODE].min_len == UBIFS_SIG_NODE_SZ), so the corrected subtraction cannot underflow. Legitimately signed images are unaffected: a correct superblock never declares a signature longer than the node it is embedded in.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 817aa094842dfc3a6b98c9582d4a647827f66201 · fixed in ab7405bd86331cc2dbc8201699d4adc33bea75e7; From 817aa094842dfc3a6b98c9582d4a647827f66201 · fixed in 11abc34698cb3172badf8aa12e623f1bac98bbd8; From 817aa094842dfc3a6b98c9582d4a647827f66201 · fixed in 8cc3da72cf57acb4b77442ea8cec48425dff7c06; From 817aa094842dfc3a6b98c9582d4a647827f66201 · fixed in 37a9d25a563f5f9103282954ce573c4a61321e7c; From 817aa094842dfc3a6b98c9582d4a647827f66201 · fixed in f76b79d6e42af20682495bccd22f72c7164b0018; From 817aa094842dfc3a6b98c9582d4a647827f66201 · fixed in a1dc246f98bb94233effa4fa3ec7bf84700bb7d1; From 817aa094842dfc3a6b98c9582d4a647827f66201 · fixed in 83e1aa9f5f906c9b1f4949d0521f0f950a159d96; From 817aa094842dfc3a6b98c9582d4a647827f66201 · fixed in 95d27c1708bb6e8823c8e7c623f9abc2a91bf4bf
- Linux Linux
5.3
- KernelLinux
From 5.3.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4
References 8
git.kernel.org
- stable/c/ab7405bd86331cc2dbc8201699d4adc33bea75e7
- stable/c/11abc34698cb3172badf8aa12e623f1bac98bbd8
- stable/c/8cc3da72cf57acb4b77442ea8cec48425dff7c06
- stable/c/37a9d25a563f5f9103282954ce573c4a61321e7c
- stable/c/f76b79d6e42af20682495bccd22f72c7164b0018
- stable/c/a1dc246f98bb94233effa4fa3ec7bf84700bb7d1
- stable/c/83e1aa9f5f906c9b1f4949d0521f0f950a159d96
- stable/c/95d27c1708bb6e8823c8e7c623f9abc2a91bf4bf