CVE-2026-99430
ocfs2: fix chunk number of the first chunk in a local quota file
No exploitation reported by the sources we read.
- Published2026-11-19
- Fixed in7.3.2 · 6.18.61 · 6.12.117
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix chunk number of the first chunk in a local quota file Mounting a crafted OCFS2 image can corrupt kernel memory. When the local quota file header of such an image claims zero chunks, the first quota entry allocated during the mount gets a chunk number taken from a kernel pointer, and releasing that entry clears a bit far outside the chunk bitmap. The write will corrupt the data stored at that address, and the corruption may lead to a system crash or damage unrelated data. Mounting requires CAP_SYS_ADMIN, so it takes an untrusted image, such as removable media or a loop mount of a file from elsewhere. Since the chunk number comes from a kernel pointer, the address of the bit that gets cleared differs from boot to boot, and the issue has been reported under several titles: - BUG: unable to handle kernel paging request in ocfs2_local_release_dquot - KASAN: use-after-free Write in ocfs2_local_release_dquot - KASAN: slab-out-of-bounds Write in ocfs2_local_release_dquot - KASAN: slab-use-after-free Write in ocfs2_local_release_dquot - KFENCE: use-after-free write in ocfs2_local_release_dquot Note that none of these is a use-after-free in the quota code: the chunk and its buffer head are alive. The bit that gets cleared lies far outside the bitmap. KASAN and KFENCE name each report based on the object occupying that address, which explains why the same issue is reported under so many different titles. In the report I sent, the address fell in a free page, which KASAN labels use-after-free. There are known reproducers. Both a syzkaller and a C reproducer are available from the Google Drive link [1] in my report thread. The issue was found by our modified syzkaller, not a theoretical thing found by an LLM. I have not seen it outside fuzzing, so it is not affecting me in the real world. The local quota file in OCFS2 is divided into chunks, and each chunk begins with a header block holding a bitmap of the quota entries that chunk has handed out. Chunks are numbered from zero, and that number is used to convert the file offset of an entry back into a bit position in the bitmap. ocfs2_local_quota_add_chunk() appends a new chunk to the in-memory list and numbers it one past the chunk that was last: list_add_tail(&chunk->qc_chunk, &oinfo->dqi_chunk); chunk->qc_num = list_entry(chunk->qc_chunk.prev, struct ocfs2_quota_chunk, qc_chunk)->qc_num + 1; The predecessor is looked up after the new chunk is added to the list, so if the list was empty, the prev pointer is the list head itself. The head is the dqi_chunk member of struct ocfs2_mem_dqinfo and is not a chunk, so reading qc_num through it lands 16 bytes past the start of the head, on the dqi_gqinode pointer that follows it. The first chunk of the file is then numbered with the lower half of a kernel pointer instead of 0. The list is empty when the local quota file header claims the file has no chunks. ocfs2_local_read_info() takes dqi_chunks from that header without validating it, so an image with dqi_chunks == 0 takes this path when the first quota entry is allocated. ocfs2_create_local_dquot() turns the bad number into a file offset with ol_dqblk_off(), which shifts a 32-bit block number left by the block size bits, so the top bits of such a large block number are lost. ocfs2_local_release_dquot() turns the offset back into a bit index with ol_dqblk_chunk_off(), using the full chunk number, so the lost bits push that index far outside the bitmap, and clearing it corrupts unrelated memory. Compute the chunk number before putting the chunk on the list, and use 0 when the list is empty.
Timeline
dates in UTC- 2026-11-1914:41CVE publishedCNA
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.3 | ≥ 6.19.0, < 7.3.2 | 7.3.2 | OSV |
| 6.x | ≥ 6.13.0, < 6.18.61 | 6.18.61 | OSV |
| 6.12 | ≥ 2.6.29, < 6.12.117 | 6.12.117 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA2 products
As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- Linuxother versions: not affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- ≥ 9e33d69f553aaf11377307e8d6f82deb3385e351, < 76986d0ad2e1b71a304db59980f7d3440709cf69fixed in 76986d0ad2e1b71a304db59980f7d3440709cf69git
- ≥ 9e33d69f553aaf11377307e8d6f82deb3385e351, < 59d336153d40649afe86ff57d3bde1ac1588e850fixed in 59d336153d40649afe86ff57d3bde1ac1588e850git
- ≥ 9e33d69f553aaf11377307e8d6f82deb3385e351, < 5778be09eab716b7d37f653d72c2c34a25f6ba05fixed in 5778be09eab716b7d37f653d72c2c34a25f6ba05git
- ≥ 9e33d69f553aaf11377307e8d6f82deb3385e351, < 4effccfd50baee4f325694964aeee997dca7bd96fixed in 4effccfd50baee4f325694964aeee997dca7bd96git
- Linuxother versions: affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- = 2.6.29no fix stated
Not affected < 2.6.29 · ≥ 6.12.117, ≤ 6.12.* · ≥ 6.18.61, ≤ 6.18.* · ≥ 7.3.2, ≤ 7.3.* · ≥ 7.4-rc1
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE terms of useCVE recordupdated 2026-11-19
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- kernelAzure Linux:3all versions · no fixed version listed
- linuxDebian:14all versions · fixed in 7.3.3-1
- linuxDebian:13all versions · fixed in 6.12.117-1
- linuxDebian:12all versions · no fixed version listed
- linux-6.12Debian:12all versions · fixed in 6.12.117-1~deb12u1
- linux-ltsAlpaquita:streamfrom 6.18.58-r0 · fixed in 6.18.62-r0
- linux-ltsAlpaquita:25from 6.12.115-r0 · no fixed version listed
- linux-ltsAlpaquita:23from 6.1.191-r1 · no fixed version listed
Vendor advisories
- CVE-2026-99430 Red Hat Product Security
kernel: kernel: Denial of Service via crafted OCFS2 image mount
Fix
- Update Linux kernel to 7.3.2 · 6.18.61 · 6.12.117
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-20
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-11-22
- CNACVSS 3.17.12026-11-22
- FIRST EPSSEPSS score0.2 %2026-11-21
- OSVaffected packages—
- GitHub Advisoriesadvisory—
Identifiers
- AZL-114863same flawAzure Linux · MIT
- EUVD-2026-130096same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-7vhf-83c4-h86csame flawGitHub Advisory Database · CC-BY-4.0
- DLA-4927-1advisory covering several CVEsDebian · LicenseRef-unstated
Technical details
- CVSS v3 vector
- CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
- Published
- 2026-11-19
- Last modified
- 2026-11-22
- NVD status
- Received
- GitHub advisory
- GHSA-7vhf-83c4-h86c
Frequently asked questions
What is CVE-2026-99430?
Is CVE-2026-99430 actively exploited?
What is the CVSS score for CVE-2026-99430?
Running Linux kernel? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website checks · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-7vhf-83c4-h86c
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- Red Hat Product Security (CSAF and VEX) · CC-BY-4.0