CVE-2026-72431
Last modified
CVE-2026-72431 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: alloc_tag: fix use-after-free in /proc/allocinfo after module unload allocinfo_start() only reinitializes the codetag iterator at position 0. For subsequent reads (position > 0), it reuses cached iterator state from the previous batch. EPSS estimates a 0.20% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: alloc_tag: fix use-after-free in /proc/allocinfo after module unload allocinfo_start() only reinitializes the codetag iterator at position 0. For subsequent reads (position > 0), it reuses cached iterator state from the previous batch. allocinfo_stop() drops mod_lock between read batches, which allows module unload to complete and free the module memory that the cached iterator still references: CPU0 (read) CPU1 (rmmod) ---- ---- allocinfo_start(pos=0) down_read(mod_lock) allocinfo_show() ... allocinfo_stop() up_read(mod_lock) codetag_unload_module() kfree(cmod) release_module_tags() ... free_mod_mem() allocinfo_start(pos=N) down_read(mod_lock) // reuses cached iter, skips re-init allocinfo_show() ct->filename <-- UAF After free_mod_mem() frees the module's .rodata, allocinfo_show() dereferences ct->filename, ct->function which point there. Save the iterator state in allocinfo_next() and resume from it in allocinfo_start() with codetag_next_ct(), which detects module removal via idr_find() returning NULL and skips to the next module.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 9f44df50fee4d2f6cb374177244ccfa9f0a5cc95, < 37e3e8a2c3bfdd503209f043f8bbfbdcf5a1d92f; >= 9f44df50fee4d2f6cb374177244ccfa9f0a5cc95, < 008ceffd44040f809aead6d7bef7cb1210c4149a; >= 9f44df50fee4d2f6cb374177244ccfa9f0a5cc95, < 2956268efc457cb05d29c1bf94de1e8e684d7bbc |
| Linux | Linux | 6.17 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-72431?
How severe is CVE-2026-72431?
How do I fix CVE-2026-72431?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-72426In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-72427In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72428In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72429In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-7243A vulnerability was identified in Totolink A8000RU 7.1cu.643…9.8
- CVE-2026-72430In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72432In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72433In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72434In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72435In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72436In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72437In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-72431?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
