CVE-2026-31435
Received Received - Intake
Use-After-Free Vulnerability in Linux Kernel netfs Read Retry

Publication date: 2026-04-22

Last updated on: 2026-04-27

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: netfs: Fix read abandonment during retry Under certain circumstances, all the remaining subrequests from a read request will get abandoned during retry. The abandonment process expects the 'subreq' variable to be set to the place to start abandonment from, but it doesn't always have a useful value (it will be uninitialised on the first pass through the loop and it may point to a deleted subrequest on later passes). Fix the first jump to "abandon:" to set subreq to the start of the first subrequest expected to need retry (which, in this abandonment case, turned out unexpectedly to no longer have NEED_RETRY set). Also clear the subreq pointer after discarding superfluous retryable subrequests to cause an oops if we do try to access it.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-22
Last Modified
2026-04-27
Generated
2026-05-07
AI Q&A
2026-04-22
EPSS Evaluated
2026-05-05
NVD
CVE-2026-31435
EUVD
EUVD-2026-24758
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :

This vulnerability in the Linux kernel's netfs subsystem can cause all remaining subrequests from a read request to be abandoned during retry under certain conditions. This may lead to unexpected behavior such as failed read operations or kernel oops (crashes) if the system tries to access an invalid subrequest pointer.


Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's netfs component, where during a read request retry, all remaining subrequests can be abandoned incorrectly. The issue arises because the variable 'subreq', which is supposed to indicate where to start abandoning subrequests, may be uninitialized or point to a deleted subrequest. This can cause improper handling of retryable subrequests.

The fix involves setting 'subreq' correctly to the first subrequest expected to need a retry and clearing the pointer after discarding unnecessary retryable subrequests to prevent invalid access.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart