CVE-2024-26831
Last modified
CVE-2024-26831 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: net/handshake: Fix handshake_req_destroy_test1 Recently, handshake_req_destroy_test1 started failing: Expected handshake_req_destroy_test == req, but handshake_req_destroy_test == 0000000000000000 req == 0000000060f99b40 not ok 11 req_destroy works This is because "sock_release(sock)" was replaced with "fput(filp)" to address a memory leak. Note that sock_release() is synchronous but fput() usually delays the final close and clean-up. The delay is not consequential in the other cases that were changed but handshake_req_destroy_test1 is testing that handshake_req_cancel() followed by closing the file actually does call the ->hp_destroy method. EPSS estimates a 0.22% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: net/handshake: Fix handshake_req_destroy_test1 Recently, handshake_req_destroy_test1 started failing: Expected handshake_req_destroy_test == req, but handshake_req_destroy_test == 0000000000000000 req == 0000000060f99b40 not ok 11 req_destroy works This is because "sock_release(sock)" was replaced with "fput(filp)" to address a memory leak. Note that sock_release() is synchronous but fput() usually delays the final close and clean-up. The delay is not consequential in the other cases that were changed but handshake_req_destroy_test1 is testing that handshake_req_cancel() followed by closing the file actually does call the ->hp_destroy method. Thus the PTR_EQ test at the end has to be sure that the final close is complete before it checks the pointer. We cannot use a completion here because if ->hp_destroy is never called (ie, there is an API bug) then the test will hang. Reported by: Guenter Roeck <linux@roeck-us.net>
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.6, < 6.6.18 | — |
| Linux | Linux Kernel | >= 6.7, < 6.7.6 | — |
| Linux | Linux Kernel | 6.5.6 | — |
| Linux | Linux Kernel | 6.8 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2024-26831?
How severe is CVE-2024-26831?
How do I fix CVE-2024-26831?
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 2024
- CVE-2024-26826In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26827Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2024-26828In the Linux kernel, the following vulnerability has been re…9.4
- CVE-2024-26829In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-2683A vulnerability classified as problematic was found in Campc…6.1
- CVE-2024-26830In the Linux kernel, the following vulnerability has been re…6.3
- CVE-2024-26832In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26833In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26834In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26835In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26836In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-26837In the Linux kernel, the following vulnerability has been re…4.7
Are you affected by CVE-2024-26831?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
