CVE-2026-99362: nfsd: preflight SEQUENCE replies before accepting a slot

Published Nov 19, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

nfsd: preflight SEQUENCE replies before accepting a slot

nfsd4sequence() narrows the reply buffer to the session's cached reply limit before it accepts the slot seqid. A client may negotiate camaxresponsesizecached down to NFSDMINHDRSEQSZ, and nfsd4allocslot() then gives every slot a zero-length sldata[]. A COMPOUND tag can fill that narrowed buffer until it holds the SEQUENCE opcode but not the status word that follows. nfsd4encodeoperation() returns without running nfsd4encodesequence(), so cstate.dataoffset stays zero. It leaves op->status at nfsok as well, so the COMPOUND is treated as having succeeded.

nfsd4storecacheentry() declines to cache a lone SEQUENCE that returned an error. That test reads the status the operation reported, so it passes here. The copy starts at offset zero and takes the whole reply, RPC and COMPOUND headers included, into the zero-length sldata[]. The COMPOUND tag is copied along with it, so the client picks most of the bytes written past the end of the slot:

BUG: KASAN: slab-out-of-bounds in readbytesfromxdrbuf+0x1bc/0x390 Write of size 80 at addr ffff888003a549cd by task kunittrycatch/24 asanmemcpy+0x38/0x60 readbytesfromxdrbuf+0x1bc/0x390 nfsd4sequencedone+0x5b0/0x810 nfs4svcencodecompoundres+0x1bf/0x240

Check that the fixed-size SEQUENCE result, plus room for a following operation's error status, fits the negotiated limit before narrowing the buffer and consuming the slot seqid. The slot and its reply cache are left unchanged, as RFC 8881 Section 2.10.6.1.2 requires of an error returned from SEQUENCE.

Affected Software

7 affected componentsFixes available
linux/kernel>=3.16.0<6.12.117
6.12.117
linux/kernel>=6.13.0<6.18.61
6.18.61
linux/kernel>=6.19.0<7.3.2
7.3.2
debian/linux*
debian/linux<6.12.117-1
6.12.117-1
debian/linux<7.3.3-1
7.3.3-1
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1
6.12.117-17.3.4-17.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.117
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.61
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.2
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.12.117-1
  5. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.3-1
  6. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1

Event History

Nov 19, 2026
CVE Published
via MITRE·02:22 PM
Data Sourced
via MITRE·02:22 PM
Description
Data Sourced
via OSV·02:22 PM
DescriptionAffected Software
Data Sourced
via NVD·03:17 PM
Description

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