CVE-2024-26831net/handshake: Fix handshake_req_destroy_test1
- 5.5MediumCVSS base score
- 0.22%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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 <[email protected]>
Timeline
ID reserved
By Linux
- 58 days later
· 58 days later
Published
- 2 years later
· 2 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 4a0f07d71b0483cc08c03cefa7c85749e187c214 – < d74226e03df1bf19848f18344401f254345af912
- affected 4a0f07d71b0483cc08c03cefa7c85749e187c214 – < 7f97805b8df6e33850e225e6bd3ebd9e246920af
- affected 4a0f07d71b0483cc08c03cefa7c85749e187c214 – < 4e1d71cabb19ec2586827adfc60d68689c68c194
- affected 1751e44980466e3ebc246d22d3ebd422197704b6
- affected 6.5.6 – < 6.6
- affected 6.6
- unaffected < 6.6
- unaffected 6.6.18 – ≤ 6.6.*
- unaffected 6.7.6 – ≤ 6.7.*
- unaffected 6.8 – ≤ *
References
References3
- https://git.kernel.org/stable/c/d74226e03df1bf19848f18344401f254345af912 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/7f97805b8df6e33850e225e6bd3ebd9e246920af (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/4e1d71cabb19ec2586827adfc60d68689c68c194 (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-24093 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-26831)Record last updated .