CVE-2026-89720

ubifs: fix out-of-bounds read in signature length check

State
Published
Severity
7.7 High
Published
Sep 11, 2026
Updated
Oct 19, 2026
Reserved
Sep 11, 2026

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
3.17.7 HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 817aa094842dfc3a6b98c9582d4a647827f66201 to before ab7405bd86331cc2dbc8201699d4adc33bea75e7Affected
  • 817aa094842dfc3a6b98c9582d4a647827f66201 to before 11abc34698cb3172badf8aa12e623f1bac98bbd8Affected
  • 817aa094842dfc3a6b98c9582d4a647827f66201 to before 8cc3da72cf57acb4b77442ea8cec48425dff7c06Affected
  • 817aa094842dfc3a6b98c9582d4a647827f66201 to before 37a9d25a563f5f9103282954ce573c4a61321e7cAffected
  • 817aa094842dfc3a6b98c9582d4a647827f66201 to before f76b79d6e42af20682495bccd22f72c7164b0018Affected
  • 817aa094842dfc3a6b98c9582d4a647827f66201 to before a1dc246f98bb94233effa4fa3ec7bf84700bb7d1Affected
  • 817aa094842dfc3a6b98c9582d4a647827f66201 to before 83e1aa9f5f906c9b1f4949d0521f0f950a159d96Affected
  • 817aa094842dfc3a6b98c9582d4a647827f66201 to before 95d27c1708bb6e8823c8e7c623f9abc2a91bf4bfAffected
LinuxLinux
  • 5.3Affected
  • before 5.3Not affected
  • 5.10.270 through 5.10.*Not affected
  • 5.15.221 through 5.15.*Not affected
  • 6.1.188 through 6.1.*Not affected
  • 6.6.157 through 6.6.*Not affected
  • 6.12.109 through 6.12.*Not affected
  • 6.18.50 through 6.18.*Not affected
  • 7.2.4 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.