acct: perform last write from workqueue
- 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.291, 5.10.235, 5.15.179, 6.1.130, 6.6.80, and 2 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: acct: perform last write from workqueue In [1] it was reported that the acct(2) system call can be used to trigger NULL deref in cases where it is set to write to a file that triggers an internal lookup. This can e.g., happen when pointing acc(2) to /sys/power/resume. At the point the where the write to this file happens the calling task has already exited and called exit_fs(). A lookup will thus trigger a NULL-deref when accessing current->fs. Reorganize the code so that the the final write happens from the workqueue but with the caller's credentials. This preserves the (strange) permission model and has almost no regression risk. This api should stop to exist though.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 8acbf4a88c6a98c8ed00afd1a7d1abcca9b4735e; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in b03782ae707cc45e65242c7cddd8e28f1c22cde5; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 5d5b936cfa4b0d5670ca7420ef165a074bc008eb; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 5ee8da9bea70dda492d61f075658939af33d8410; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 5c928e14a2ccd99462f2351ead627b58075bb736; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 5a59ced8ffc71973d42c82484a719c8f6ac8f7f7; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in a8136afca090412a36429cb6c2543c714d9c0f84; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 56d5f3eba3f5de0efdd556de4ef381e109b973a9
- Linux Linux
2.6.12
- KernelLinux
From 2.6.12 · fixed in 5.4.291; From 5.5.0 · fixed in 5.10.235; From 5.11.0 · fixed in 5.15.179; From 5.16.0 · fixed in 6.1.130; From 6.2.0 · fixed in 6.6.80; From 6.7.0 · fixed in 6.12.17; From 6.13.0 · fixed in 6.13.5
References 8
git.kernel.org
- stable/c/8acbf4a88c6a98c8ed00afd1a7d1abcca9b4735e
- stable/c/b03782ae707cc45e65242c7cddd8e28f1c22cde5
- stable/c/5d5b936cfa4b0d5670ca7420ef165a074bc008eb
- stable/c/5ee8da9bea70dda492d61f075658939af33d8410
- stable/c/5c928e14a2ccd99462f2351ead627b58075bb736
- stable/c/5a59ced8ffc71973d42c82484a719c8f6ac8f7f7
- stable/c/a8136afca090412a36429cb6c2543c714d9c0f84
- stable/c/56d5f3eba3f5de0efdd556de4ef381e109b973a9