NFSD: Avoid calling OPDESC() with ops->opnum == OP_ILLEGAL
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.220, 5.15.107, 6.1.24, 6.2.11
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: NFSD: Avoid calling OPDESC() with ops->opnum == OP_ILLEGAL OPDESC() simply indexes into nfsd4_ops[] by the op's operation number, without range checking that value. It assumes callers are careful to avoid calling it with an out-of-bounds opnum value. nfsd4_decode_compound() is not so careful, and can invoke OPDESC() with opnum set to OP_ILLEGAL, which is 10044 -- well beyond the end of nfsd4_ops[].
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From f4f9ef4a1b0a1ca80b152e28e176d69515bdf7e8 · fixed in 50827896c365e0f6c8b55ed56d444dafd87c92c5; From f4f9ef4a1b0a1ca80b152e28e176d69515bdf7e8 · fixed in a64160124d5a078be0c380b1e8a0bad2d040d3a1; From f4f9ef4a1b0a1ca80b152e28e176d69515bdf7e8 · fixed in ffcbcf087581ae68ddc0a21460f7ecd4315bdd0e; From f4f9ef4a1b0a1ca80b152e28e176d69515bdf7e8 · fixed in f352c41fa718482979e7e6b71b4da2b718e381cc; From f4f9ef4a1b0a1ca80b152e28e176d69515bdf7e8 · fixed in 804d8e0a6e54427268790472781e03bc243f4ee3
- Linux Linux
4.14
- KernelLinux
From 4.14.0 · fixed in 5.10.220; From 5.11.0 · fixed in 5.15.107; From 5.16.0 · fixed in 6.1.24; From 6.2.0 · fixed in 6.2.11