CVE-2026-43076 json
ocfs2: validate inline data i_size during inode read
published 2026-05-06 6 mo ago modified 2026-08-05 3 mo ago also EUVD-2026-27563
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: validate inline data i_size during inode read
When reading an inode from disk, ocfs2_validate_inode_block() performs various sanity checks but does not validate the size of inline data. If the filesystem is corrupted, an inode's i_size can exceed the actual inline data capacity (id_count).
This causes ocfs2_dir_foreach_blk_id() to iterate beyond the inline data buffer, triggering a use-after-free when accessing directory entries from freed memory.
In the syzbot report: - i_size was 1099511627576 bytes (~1TB) - Actual inline data capacity (id_count) is typically <256 bytes - A garbage rec_len (54648) caused ctx->pos to jump out of bounds - This triggered a UAF in ocfs2_check_dir_entry()
Fix by adding a validation check in ocfs2_validate_inode_block() to ensure inodes with inline data have i_size <= id_count. This catches the corruption early during inode read and prevents all downstream code from operating on invalid data.
Patch / fix
- Linux Linux 5.10.258, 5.15.209, 6.1.175, 6.6.136, 6.12.83, 6.18.24, 6.19.14, 7.0
- linux Debian 12 6.1.176-1
- linux Debian 13 6.12.85-1
- linux Debian 14 6.19.14-1
debian advisories DEBIAN-CVE-2026-43076
- linux Ubuntu 22.04 LTS 5.15.0-186.196
- linux Ubuntu 24.04 LTS 6.8.0-136.136
- linux-aws Ubuntu 22.04 LTS 5.15.0-1112.119
- linux-aws Ubuntu 24.04 LTS 6.8.0-1061.64
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1112.122
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1064.72
- linux-gke Ubuntu 22.04 LTS 5.15.0-1108.114
- linux-gke Ubuntu 24.04 LTS 6.8.0-1059.67
ubuntu advisories UBUNTU-CVE-2026-43076
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/d012c782abcabe68b5b9e71be58a15e9f9d83dc1 commit
- git.kernel.org/stable/c/bcd46bc261b215b3b12c557a978299eafa02ecdd commit
- git.kernel.org/stable/c/131c0b573e1b467b7d553e9ff38003f1acd8f5f2 commit
- git.kernel.org/stable/c/37f074e65f24f10f8d8df224a572e4cb9e6faf63 commit
- git.kernel.org/stable/c/c1de19e891be3bfb3e1d0c7cf07bbb8fb3b77c1b commit
- git.kernel.org/stable/c/cd2d765aa7157f852999842af32148128c735d39 commit
- git.kernel.org/stable/c/77d0295725109d77f5854ef5b58c0d06c08168cc commit
- git.kernel.org/stable/c/1524af3685b35feac76662cc551cbc37bd14775f commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-43076 updated
kernel: ocfs2: validate inline data i_size during inode read
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
- git.kernel.org /stable/c/d012c782abcabe68b5b9e71be58a15e9f9d83dc1
- git.kernel.org /stable/c/bcd46bc261b215b3b12c557a978299eafa02ecdd
- git.kernel.org /stable/c/131c0b573e1b467b7d553e9ff38003f1acd8f5f2
-
git.kernel.org
/stable/c/37f074e65f24f10f8d8df224a572e4cb9e6faf63
patch
-
git.kernel.org
/stable/c/c1de19e891be3bfb3e1d0c7cf07bbb8fb3b77c1b
patch
-
git.kernel.org
/stable/c/cd2d765aa7157f852999842af32148128c735d39
patch
-
git.kernel.org
/stable/c/77d0295725109d77f5854ef5b58c0d06c08168cc
patch
-
git.kernel.org
/stable/c/1524af3685b35feac76662cc551cbc37bd14775f
patch
Sources
- CVE List CVE-2026-43076
- NVD CVE-2026-43076
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.