CVE-2026-43178
7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved:
procfs: fix possible double mmput() in do_procmap_query()
When user provides incorrectly sized buffer for build ID for PROCMAP_QUERY we return with -ENAMETOOLONG error. After recent changes this condition happens later, after we unlocked mmap_lock/per-VMA lock and did mmput(), so original goto out is now wrong and will double-mmput() mm_struct. Fix by jumping further to clean up only vm_file and name_buf.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Linux | Linux | b9b97e6aeb534315f9646b2090d1a5024c6a4e82 < f9fe092084cd04deea18747f58a2304026e76aaa | affected |
| Linux | Linux | cbc03ce3e6ce7e21214c3f02218213574c1a2d08 < 8adaff87db143583e08eec4f4e7788f1ef8af94d | affected |
| Linux | Linux | b5cbacd7f86f4f62b8813688c8e73be94e8e1951 < 90f5e87c9b75833b9ef3a4415b92c0247f28ab2f | affected |
| Linux | Linux | b5cbacd7f86f4f62b8813688c8e73be94e8e1951 < 61dc9f776705d6db6847c101b98fa4f0e9eb6fa3 | affected |
| Linux | Linux | 6.12.70 < 6.12.75 | affected |
| Linux | Linux | 6.18.10 < 6.18.16 | affected |
| Linux | Linux | 6.19 | affected |
| Linux | Linux | 0 < 6.19 | unaffected |
| Linux | Linux | 6.12.75 <= 6.12.* | unaffected |
| Linux | Linux | 6.18.16 <= 6.18.* | unaffected |
| Linux | Linux | 6.19.6 <= 6.19.* | unaffected |
| Linux | Linux | 7.0 <= * | unaffected |
Weaknesses
ADP Enrichment
kernel: procfs: fix possible double mmput() in do_procmap_query()
Additional References
- https://access.redhat.com/security/cve/CVE-2026-43178
- https://bugzilla.redhat.com/show_bug.cgi?id=2467227
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-43178.json
References
- https://git.kernel.org/stable/c/f9fe092084cd04deea18747f58a2304026e76aaa
- https://git.kernel.org/stable/c/8adaff87db143583e08eec4f4e7788f1ef8af94d
- https://git.kernel.org/stable/c/90f5e87c9b75833b9ef3a4415b92c0247f28ab2f
- https://git.kernel.org/stable/c/61dc9f776705d6db6847c101b98fa4f0e9eb6fa3
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.