GHSA-H9FX-4JCW-948X
Vulnerability from github – Published: 2026-10-28 12:31 – Updated: 2026-10-30 15:34In the Linux kernel, the following vulnerability has been resolved:
ext4: free the sbi after a grace period
ext4_get_link() follows a symlink that keeps its target in a data block in rcu pathwalk mode with ext4_getblk(EXT4_GET_BLOCKS_CACHED_NOWAIT). That reads s_mount_state in the ASSERT() of ext4_getblk() and again in ext4_es_lookup_extent(), and the lookup bumps the extent status hit or miss counter, all through sb->s_fs_info.
ext4_put_super() destroys those counters, clears sb->s_fs_info and frees the sbi without waiting for a grace period. A pathwalk that is still in ext4_get_link() when the last reference to the mount goes away then dereferences a NULL s_fs_info, the freed sbi or the destroyed percpu counters.
With a pathwalk held up in ext4_get_link() while the last reference goes away:
KASAN: null-ptr-deref in range [0x00000000000000a8-0x00000000000000af] RIP: 0010:ext4_getblk+0xf0/0x640 Call Trace: ext4_get_link+0x26c/0x410 pick_link+0xf96/0x1780 step_into_slowpath+0x9b8/0x1250 path_lookupat+0x484/0xb00 filename_lookup+0x1f1/0x5b0 vfs_statx+0xd7/0x3b0 vfs_fstatat+0x4d/0x90 __do_sys_newfstatat+0xa0/0x100 do_syscall_64+0x10e/0x5e0 entry_SYSCALL_64_after_hwframe+0x77/0x7f
So far that has been hard to hit. umount(2) waits for a grace period in namespace_unlock() before it drops the mount, so only a mount whose last reference goes away elsewhere, like the close of a file or a chdir out of a lazily unmounted directory, can race a walker.
Keep sb->s_fs_info and free the sbi together with the extent status counters after a grace period. Split the counters out of ext4_es_unregister_shrinker() for that. The shrinker still gets wasted in ext4_put_super(), the counters go with the sbi.
{
"affected": [],
"aliases": [
"CVE-2026-99174"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-28T11:17:38Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\next4: free the sbi after a grace period\n\next4_get_link() follows a symlink that keeps its target in a data block\nin rcu pathwalk mode with ext4_getblk(EXT4_GET_BLOCKS_CACHED_NOWAIT).\nThat reads s_mount_state in the ASSERT() of ext4_getblk() and again in\next4_es_lookup_extent(), and the lookup bumps the extent status hit or\nmiss counter, all through sb-\u003es_fs_info.\n\next4_put_super() destroys those counters, clears sb-\u003es_fs_info and frees\nthe sbi without waiting for a grace period. A pathwalk that is still in\next4_get_link() when the last reference to the mount goes away then\ndereferences a NULL s_fs_info, the freed sbi or the destroyed percpu\ncounters.\n\nWith a pathwalk held up in ext4_get_link() while the last reference\ngoes away:\n\n KASAN: null-ptr-deref in range [0x00000000000000a8-0x00000000000000af]\n RIP: 0010:ext4_getblk+0xf0/0x640\n Call Trace:\n \u003cTASK\u003e\n ext4_get_link+0x26c/0x410\n pick_link+0xf96/0x1780\n step_into_slowpath+0x9b8/0x1250\n path_lookupat+0x484/0xb00\n filename_lookup+0x1f1/0x5b0\n vfs_statx+0xd7/0x3b0\n vfs_fstatat+0x4d/0x90\n __do_sys_newfstatat+0xa0/0x100\n do_syscall_64+0x10e/0x5e0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nSo far that has been hard to hit. umount(2) waits for a grace period in\nnamespace_unlock() before it drops the mount, so only a mount whose last\nreference goes away elsewhere, like the close of a file or a chdir out of\na lazily unmounted directory, can race a walker.\n\nKeep sb-\u003es_fs_info and free the sbi together with the extent status\ncounters after a grace period. Split the counters out of\next4_es_unregister_shrinker() for that. The shrinker still gets wasted\nin ext4_put_super(), the counters go with the sbi.",
"id": "GHSA-h9fx-4jcw-948x",
"modified": "2026-10-30T15:34:23Z",
"published": "2026-10-28T12:31:06Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99174"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4ce0e27ea610663a9cdc04e3bca38559147428d4"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/80d5db1686b05fad6f384be017714297d828a714"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/87d29b8b849738d52fe820d495fa0aa2d5a1ec82"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b4b0598fad51a978fcbda9d55eef6b5bd3cbe7d8"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c17b44266a1f9fcb49b894d4611d1254bf1aa313"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/cf3bd5824c985b350d150bcd76698ee5e993fcba"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
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.