CVE-2026-99430 (GCVE-0-2026-99430)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:41 – Updated: 2026-11-19 14:41| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
9e33d69f553aaf11377307e8d6f82deb3385e351 , < 76986d0ad2e1b71a304db59980f7d3440709cf69
(git)
Affected: 9e33d69f553aaf11377307e8d6f82deb3385e351 , < 59d336153d40649afe86ff57d3bde1ac1588e850 (git) Affected: 9e33d69f553aaf11377307e8d6f82deb3385e351 , < 5778be09eab716b7d37f653d72c2c34a25f6ba05 (git) Affected: 9e33d69f553aaf11377307e8d6f82deb3385e351 , < 4effccfd50baee4f325694964aeee997dca7bd96 (git) |
guessed | |
| Linux | Linux |
Affected:
2.6.29
Unaffected: 0 , < 2.6.29 (semver) Unaffected: 6.12.117 , ≤ 6.12.* (semver) Unaffected: 6.18.61 , ≤ 6.18.* (semver) Unaffected: 7.3.2 , ≤ 7.3.* (semver) Unaffected: 7.4-rc1 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/ocfs2/quota_local.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "76986d0ad2e1b71a304db59980f7d3440709cf69",
"status": "affected",
"version": "9e33d69f553aaf11377307e8d6f82deb3385e351",
"versionType": "git"
},
{
"lessThan": "59d336153d40649afe86ff57d3bde1ac1588e850",
"status": "affected",
"version": "9e33d69f553aaf11377307e8d6f82deb3385e351",
"versionType": "git"
},
{
"lessThan": "5778be09eab716b7d37f653d72c2c34a25f6ba05",
"status": "affected",
"version": "9e33d69f553aaf11377307e8d6f82deb3385e351",
"versionType": "git"
},
{
"lessThan": "4effccfd50baee4f325694964aeee997dca7bd96",
"status": "affected",
"version": "9e33d69f553aaf11377307e8d6f82deb3385e351",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/ocfs2/quota_local.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "2.6.29"
},
{
"lessThan": "2.6.29",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.117",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.61",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.2",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.117",
"versionStartIncluding": "2.6.29",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.61",
"versionStartIncluding": "2.6.29",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.2",
"versionStartIncluding": "2.6.29",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc1",
"versionStartIncluding": "2.6.29",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: fix chunk number of the first chunk in a local quota file\n\nMounting a crafted OCFS2 image can corrupt kernel memory. When the\nlocal quota file header of such an image claims zero chunks, the first\nquota entry allocated during the mount gets a chunk number taken from a\nkernel pointer, and releasing that entry clears a bit far outside the\nchunk bitmap.\n\nThe write will corrupt the data stored at that address, and the\ncorruption may lead to a system crash or damage unrelated data. \nMounting requires CAP_SYS_ADMIN, so it takes an untrusted image, such\nas removable media or a loop mount of a file from elsewhere.\n\nSince the chunk number comes from a kernel pointer, the address of the\nbit that gets cleared differs from boot to boot, and the issue has been\nreported under several titles:\n\n- BUG: unable to handle kernel paging request in ocfs2_local_release_dquot\n- KASAN: use-after-free Write in ocfs2_local_release_dquot\n- KASAN: slab-out-of-bounds Write in ocfs2_local_release_dquot\n- KASAN: slab-use-after-free Write in ocfs2_local_release_dquot\n- KFENCE: use-after-free write in ocfs2_local_release_dquot\n\nNote that none of these is a use-after-free in the quota code: the\nchunk and its buffer head are alive. The bit that gets cleared lies\nfar outside the bitmap. KASAN and KFENCE name each report based on the\nobject occupying that address, which explains why the same issue is\nreported under so many different titles. In the report I sent, the\naddress fell in a free page, which KASAN labels use-after-free.\n\nThere are known reproducers. Both a syzkaller and a C reproducer are\navailable from the Google Drive link [1] in my report thread. The\nissue was found by our modified syzkaller, not a theoretical thing\nfound by an LLM. I have not seen it outside fuzzing, so it is not\naffecting me in the real world.\n\nThe local quota file in OCFS2 is divided into chunks, and each chunk\nbegins with a header block holding a bitmap of the quota entries that\nchunk has handed out. Chunks are numbered from zero, and that number is\nused to convert the file offset of an entry back into a bit position in\nthe bitmap. ocfs2_local_quota_add_chunk() appends a new chunk to the\nin-memory list and numbers it one past the chunk that was last:\n\n\tlist_add_tail(\u0026chunk-\u003eqc_chunk, \u0026oinfo-\u003edqi_chunk);\n\tchunk-\u003eqc_num = list_entry(chunk-\u003eqc_chunk.prev,\n\t\t\t\t struct ocfs2_quota_chunk,\n\t\t\t\t qc_chunk)-\u003eqc_num + 1;\n\nThe predecessor is looked up after the new chunk is added to the list, so\nif the list was empty, the prev pointer is the list head itself. The head\nis the dqi_chunk member of struct ocfs2_mem_dqinfo and is not a chunk, so\nreading qc_num through it lands 16 bytes past the start of the head, on\nthe dqi_gqinode pointer that follows it. The first chunk of the file is\nthen numbered with the lower half of a kernel pointer instead of 0.\n\nThe list is empty when the local quota file header claims the file has no\nchunks. ocfs2_local_read_info() takes dqi_chunks from that header without\nvalidating it, so an image with dqi_chunks == 0 takes this path when the\nfirst quota entry is allocated.\n\nocfs2_create_local_dquot() turns the bad number into a file offset with\nol_dqblk_off(), which shifts a 32-bit block number left by the block size\nbits, so the top bits of such a large block number are lost. \nocfs2_local_release_dquot() turns the offset back into a bit index with\nol_dqblk_chunk_off(), using the full chunk number, so the lost bits push\nthat index far outside the bitmap, and clearing it corrupts unrelated\nmemory.\n\nCompute the chunk number before putting the chunk on the list, and use 0\nwhen the list is empty."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:41:03.138Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/76986d0ad2e1b71a304db59980f7d3440709cf69"
},
{
"url": "https://git.kernel.org/stable/c/59d336153d40649afe86ff57d3bde1ac1588e850"
},
{
"url": "https://git.kernel.org/stable/c/5778be09eab716b7d37f653d72c2c34a25f6ba05"
},
{
"url": "https://git.kernel.org/stable/c/4effccfd50baee4f325694964aeee997dca7bd96"
}
],
"title": "ocfs2: fix chunk number of the first chunk in a local quota file",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99430",
"datePublished": "2026-11-19T14:41:03.138Z",
"dateReserved": "2026-09-25T10:25:14.414Z",
"dateUpdated": "2026-11-19T14:41:03.138Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/ocfs2/quota_local.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "76986d0ad2e1b71a304db59980f7d3440709cf69",
"status": "affected",
"version": "9e33d69f553aaf11377307e8d6f82deb3385e351",
"versionType": "git"
},
{
"lessThan": "59d336153d40649afe86ff57d3bde1ac1588e850",
"status": "affected",
"version": "9e33d69f553aaf11377307e8d6f82deb3385e351",
"versionType": "git"
},
{
"lessThan": "5778be09eab716b7d37f653d72c2c34a25f6ba05",
"status": "affected",
"version": "9e33d69f553aaf11377307e8d6f82deb3385e351",
"versionType": "git"
},
{
"lessThan": "4effccfd50baee4f325694964aeee997dca7bd96",
"status": "affected",
"version": "9e33d69f553aaf11377307e8d6f82deb3385e351",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/ocfs2/quota_local.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "2.6.29"
},
{
"lessThan": "2.6.29",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.117",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.61",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.2",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: fix chunk number of the first chunk in a local quota file\n\nMounting a crafted OCFS2 image can corrupt kernel memory. When the\nlocal quota file header of such an image claims zero chunks, the first\nquota entry allocated during the mount gets a chunk number taken from a\nkernel pointer, and releasing that entry clears a bit far outside the\nchunk bitmap.\n\nThe write will corrupt the data stored at that address, and the\ncorruption may lead to a system crash or damage unrelated data. \nMounting requires CAP_SYS_ADMIN, so it takes an untrusted image, such\nas removable media or a loop mount of a file from elsewhere.\n\nSince the chunk number comes from a kernel pointer, the address of the\nbit that gets cleared differs from boot to boot, and the issue has been\nreported under several titles:\n\n- BUG: unable to handle kernel paging request in ocfs2_local_release_dquot\n- KASAN: use-after-free Write in ocfs2_local_release_dquot\n- KASAN: slab-out-of-bounds Write in ocfs2_local_release_dquot\n- KASAN: slab-use-after-free Write in ocfs2_local_release_dquot\n- KFENCE: use-after-free write in ocfs2_local_release_dquot\n\nNote that none of these is a use-after-free in the quota code: the\nchunk and its buffer head are alive. The bit that gets cleared lies\nfar outside the bitmap. KASAN and KFENCE name each report based on the\nobject occupying that address, which explains why the same issue is\nreported under so many different titles. In the report I sent, the\naddress fell in a free page, which KASAN labels use-after-free.\n\nThere are known reproducers. Both a syzkaller and a C reproducer are\navailable from the Google Drive link [1] in my report thread. The\nissue was found by our modified syzkaller, not a theoretical thing\nfound by an LLM. I have not seen it outside fuzzing, so it is not\naffecting me in the real world.\n\nThe local quota file in OCFS2 is divided into chunks, and each chunk\nbegins with a header block holding a bitmap of the quota entries that\nchunk has handed out. Chunks are numbered from zero, and that number is\nused to convert the file offset of an entry back into a bit position in\nthe bitmap. ocfs2_local_quota_add_chunk() appends a new chunk to the\nin-memory list and numbers it one past the chunk that was last:\n\n\tlist_add_tail(\u0026chunk-\u003eqc_chunk, \u0026oinfo-\u003edqi_chunk);\n\tchunk-\u003eqc_num = list_entry(chunk-\u003eqc_chunk.prev,\n\t\t\t\t struct ocfs2_quota_chunk,\n\t\t\t\t qc_chunk)-\u003eqc_num + 1;\n\nThe predecessor is looked up after the new chunk is added to the list, so\nif the list was empty, the prev pointer is the list head itself. The head\nis the dqi_chunk member of struct ocfs2_mem_dqinfo and is not a chunk, so\nreading qc_num through it lands 16 bytes past the start of the head, on\nthe dqi_gqinode pointer that follows it. The first chunk of the file is\nthen numbered with the lower half of a kernel pointer instead of 0.\n\nThe list is empty when the local quota file header claims the file has no\nchunks. ocfs2_local_read_info() takes dqi_chunks from that header without\nvalidating it, so an image with dqi_chunks == 0 takes this path when the\nfirst quota entry is allocated.\n\nocfs2_create_local_dquot() turns the bad number into a file offset with\nol_dqblk_off(), which shifts a 32-bit block number left by the block size\nbits, so the top bits of such a large block number are lost. \nocfs2_local_release_dquot() turns the offset back into a bit index with\nol_dqblk_chunk_off(), using the full chunk number, so the lost bits push\nthat index far outside the bitmap, and clearing it corrupts unrelated\nmemory.\n\nCompute the chunk number before putting the chunk on the list, and use 0\nwhen the list is empty."
}
],
"id": "CVE-2026-99430",
"lastModified": "2026-11-19T15:17:56.240",
"metrics": {},
"published": "2026-11-19T15:17:56.240",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/4effccfd50baee4f325694964aeee997dca7bd96"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/5778be09eab716b7d37f653d72c2c34a25f6ba05"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/59d336153d40649afe86ff57d3bde1ac1588e850"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/76986d0ad2e1b71a304db59980f7d3440709cf69"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-19T21:37:44+00:00",
"cve": "CVE-2026-99430",
"id": "CVE-2026-99430",
"initial_release_date": "2026-11-19T14:41:03.138000+00:00",
"product_status:known_not_affected": "204",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Denial of Service via crafted OCFS2 image mount",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99430.json",
"version": "3"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.