sctp: sysctl: rto_min/max: avoid using current->nsproxy
- 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.4.290, 5.10.234, 5.15.177, 6.1.125, 6.6.72, and 1 more
- 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: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: rto_min/max: avoid using current->nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: • Inconsistency: getting info from the reader's/writer's netns vs only from the opener's netns. • current->nsproxy can be NULL in some cases, resulting in an 'Oops' (null-ptr-deref), e.g. when the current task is exiting, as spotted by syzbot [1] using acct(2). The 'net' structure can be obtained from the table->data using container_of(). Note that table->data could also be used directly, as this is the only member needed from the 'net' structure, but that would increase the size of this fix, to use '*data' everywhere 'net->sctp.rto_min/max' is used.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 4f3fdf3bc59cafd14c3bc2c2369efad34c7aa8b5 · fixed in c8d179f3b1c1d60bf4484f50aa67b4c70f91bff9; From 4f3fdf3bc59cafd14c3bc2c2369efad34c7aa8b5 · fixed in 246428bfb9e7db15c5cd08e1d0eca41b65af2b06; From 4f3fdf3bc59cafd14c3bc2c2369efad34c7aa8b5 · fixed in 0f78f09466744589e420935e646ae78212a38290; From 4f3fdf3bc59cafd14c3bc2c2369efad34c7aa8b5 · fixed in 4059507e34aa5fe0fa9fd5b2b5f0c8b26ab2d482; From 4f3fdf3bc59cafd14c3bc2c2369efad34c7aa8b5 · fixed in dc9d0e3cfd16f66fbf0862857c6b391c8613ca9f; From 4f3fdf3bc59cafd14c3bc2c2369efad34c7aa8b5 · fixed in c87f1f6ade56c711f8736901e330685b453e420e; From 4f3fdf3bc59cafd14c3bc2c2369efad34c7aa8b5 · fixed in 9fc17b76fc70763780aa78b38fcf4742384044a5
- Linux Linux
3.13
- KernelLinux
From 3.13.0 · fixed in 5.4.290; From 5.5.0 · fixed in 5.10.234; From 5.11.0 · fixed in 5.15.177; From 5.16.0 · fixed in 6.1.125; From 6.2.0 · fixed in 6.6.72; From 6.7.0 · fixed in 6.12.10
References 7
git.kernel.org
- stable/c/c8d179f3b1c1d60bf4484f50aa67b4c70f91bff9
- stable/c/246428bfb9e7db15c5cd08e1d0eca41b65af2b06
- stable/c/0f78f09466744589e420935e646ae78212a38290
- stable/c/4059507e34aa5fe0fa9fd5b2b5f0c8b26ab2d482
- stable/c/dc9d0e3cfd16f66fbf0862857c6b391c8613ca9f
- stable/c/c87f1f6ade56c711f8736901e330685b453e420e
- stable/c/9fc17b76fc70763780aa78b38fcf4742384044a5