CVE-2026-31435: netfs: Fix read abandonment during retry

Published Apr 22, 2026
·
Updated

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 NEEDRETRY set).

Also clear the subreq pointer after discarding superfluous retryable subrequests to cause an oops if we do try to access it.

Affected Software

9 affected components
Linux Linux kernel (netfs)
Linux Linux kernel>=6.12<6.18.21
Linux Linux kernel>=6.19<6.19.11
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
Linux Linux kernel=7.0-rc5
Linux Linux kernel=7.0-rc6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    For the Linux kernel vulnerability described ("netfs: Fix read abandonment during retry"), ensure the fix is applied so that read abandonment during retry no longer risks OOPS from accessing a deleted or uninitialised subrequest (set subreq to the start of the first jump to "abandon:" and clear the subreq pointer after discarding superfluous retryable).

Event History

Apr 22, 2026
CVE Published
via MITRE·01:53 PM
Data Sourced
via MITRE·01:53 PM
DescriptionSeverity
Data Sourced
via NVD·02:16 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What does the supplied severity vector indicate about exploitation prerequisites?

The vector indicates network reachability, low attack complexity, no privileges required, and required user interaction. It also rates confidentiality, integrity, and availability impact as high if exploitation succeeds.

2

Is a fix available, and are fixed kernel versions identified?

The issue is described as resolved, and three stable kernel commit references are provided. The supplied data does not identify affected or fixed kernel version ranges.

3

Does the available information say whether a default kernel configuration is affected?

No. The supplied information identifies the netfs component and a read-retry condition, but does not state whether netfs is enabled or reachable in a default configuration.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203