CVE-2026-99574 (GCVE-0-2026-99574)
Vulnerability from cvelistv5 – Published: 2026-11-20 05:49 – Updated: 2026-11-20 05:49| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 , < ddb9848fd6b2f4e9ed5ef78b20c9720c65a29df5
(git)
Affected: 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 , < 9b08fc2d092171af388f83030d54488b87453155 (git) Affected: 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 , < 7f88cd38394a16c326073c8813e7f1f1445bf3ba (git) Affected: 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 , < 080833a32fd5dc10b3acf2fa9af9b3213e6cb617 (git) |
guessed | |
| Linux | Linux |
Affected:
3.8
Unaffected: 0 , < 3.8 (semver) Unaffected: 6.12.118 , ≤ 6.12.* (semver) Unaffected: 6.18.64 , ≤ 6.18.* (semver) Unaffected: 7.3.5 , ≤ 7.3.* (semver) Unaffected: 7.4-rc1 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/f2fs/super.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "ddb9848fd6b2f4e9ed5ef78b20c9720c65a29df5",
"status": "affected",
"version": "39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5",
"versionType": "git"
},
{
"lessThan": "9b08fc2d092171af388f83030d54488b87453155",
"status": "affected",
"version": "39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5",
"versionType": "git"
},
{
"lessThan": "7f88cd38394a16c326073c8813e7f1f1445bf3ba",
"status": "affected",
"version": "39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5",
"versionType": "git"
},
{
"lessThan": "080833a32fd5dc10b3acf2fa9af9b3213e6cb617",
"status": "affected",
"version": "39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/f2fs/super.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "3.8"
},
{
"lessThan": "3.8",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"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.118",
"versionStartIncluding": "3.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.64",
"versionStartIncluding": "3.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.5",
"versionStartIncluding": "3.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc1",
"versionStartIncluding": "3.8",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: bound the SIT/NAT bitmaps by the checkpoint pack\n\nsit_ver_bitmap_bytesize and nat_ver_bitmap_bytesize are used as memcpy\nlengths into and out of sbi-\u003eckpt, which is sized from cp_payload alone,\nand nothing compares either length against that allocation.\n\nsanity_check_ckpt() has checked these two fields since c77ec61ca0a4, which\nadded them after a crafted image overran build_sit_info(). That check ties\neach length to a segment count; it never compares either against the\nallocation, which is the half this adds.\n\nMounting over-reads in build_sit_info() and build_node_manager(), and the\nfirst checkpoint writes the same lengths back through the same pointers,\nso the over-read\u0027s contents reach the on-disk checkpoint. An unmount is\nenough; the filesystem does not have to be used.\n\nBound both ends the way __bitmap_ptr() lays them out. The three branches\ndiffer, so a single sum of the two lengths would still admit a small\noverflow when cp_payload is non-zero."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T05:49:07.960Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/ddb9848fd6b2f4e9ed5ef78b20c9720c65a29df5"
},
{
"url": "https://git.kernel.org/stable/c/9b08fc2d092171af388f83030d54488b87453155"
},
{
"url": "https://git.kernel.org/stable/c/7f88cd38394a16c326073c8813e7f1f1445bf3ba"
},
{
"url": "https://git.kernel.org/stable/c/080833a32fd5dc10b3acf2fa9af9b3213e6cb617"
}
],
"title": "f2fs: bound the SIT/NAT bitmaps by the checkpoint pack",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99574",
"datePublished": "2026-11-20T05:49:07.960Z",
"dateReserved": "2026-09-25T10:25:14.422Z",
"dateUpdated": "2026-11-20T05:49:07.960Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-99574",
"date": "2026-11-21",
"epss": "0.00201",
"percentile": "0.09918"
},
"microsoft_vex": {
"current_release_date": "2026-11-21T01:13:30.000Z",
"cve": "CVE-2026-99574",
"id": "msrc_CVE-2026-99574",
"initial_release_date": "2026-11-20T18:08:46.000Z",
"product_status:known_affected": "1",
"product_status:under_investigation": "1",
"source": "Microsoft CSAF VEX",
"status": "final",
"title": "f2fs: bound the SIT/NAT bitmaps by the checkpoint pack",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-99574.json",
"version": "2"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/f2fs/super.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "ddb9848fd6b2f4e9ed5ef78b20c9720c65a29df5",
"status": "affected",
"version": "39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5",
"versionType": "git"
},
{
"lessThan": "9b08fc2d092171af388f83030d54488b87453155",
"status": "affected",
"version": "39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5",
"versionType": "git"
},
{
"lessThan": "7f88cd38394a16c326073c8813e7f1f1445bf3ba",
"status": "affected",
"version": "39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5",
"versionType": "git"
},
{
"lessThan": "080833a32fd5dc10b3acf2fa9af9b3213e6cb617",
"status": "affected",
"version": "39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/f2fs/super.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "3.8"
},
{
"lessThan": "3.8",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"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\nf2fs: bound the SIT/NAT bitmaps by the checkpoint pack\n\nsit_ver_bitmap_bytesize and nat_ver_bitmap_bytesize are used as memcpy\nlengths into and out of sbi-\u003eckpt, which is sized from cp_payload alone,\nand nothing compares either length against that allocation.\n\nsanity_check_ckpt() has checked these two fields since c77ec61ca0a4, which\nadded them after a crafted image overran build_sit_info(). That check ties\neach length to a segment count; it never compares either against the\nallocation, which is the half this adds.\n\nMounting over-reads in build_sit_info() and build_node_manager(), and the\nfirst checkpoint writes the same lengths back through the same pointers,\nso the over-read\u0027s contents reach the on-disk checkpoint. An unmount is\nenough; the filesystem does not have to be used.\n\nBound both ends the way __bitmap_ptr() lays them out. The three branches\ndiffer, so a single sum of the two lengths would still admit a small\noverflow when cp_payload is non-zero."
}
],
"id": "CVE-2026-99574",
"lastModified": "2026-11-20T06:17:48.457",
"metrics": {},
"published": "2026-11-20T06:17:48.457",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/080833a32fd5dc10b3acf2fa9af9b3213e6cb617"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/7f88cd38394a16c326073c8813e7f1f1445bf3ba"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/9b08fc2d092171af388f83030d54488b87453155"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/ddb9848fd6b2f4e9ed5ef78b20c9720c65a29df5"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-20T10:19:32+00:00",
"cve": "CVE-2026-99574",
"id": "CVE-2026-99574",
"initial_release_date": "2026-11-20T05:49:07.960000+00:00",
"product_status:known_not_affected": "204",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Information disclosure in f2fs via crafted checkpoint bitmaps",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99574.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-11-20T17:46:21Z",
"cve": "CVE-2026-99574",
"id": "CVE-2026-99574",
"initial_release_date": "2026-11-20T17:46:21Z",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-99574",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2026/cve-2026-99574.json",
"version": "2"
}
}
}
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.