xfs: don't overrun incore inode when cleaning attr forks
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel c28b4b48deac17749ed1ebe4289a4ba73541ddc6, Kernel 471e4ae43cc5f931430f7701df45ce82c8afc05d, Kernel 4a6217e7bdf3b1cdd28799d19c175cb3bad375ec and 4 more.
In the Linux kernel, the following vulnerability has been resolved: xfs: don't overrun incore inode when cleaning attr forks LOLLM noticed that xrep_dinode_check_afork doesn't check for a di_forkoff value that is so large that the attr fork would begin after the end of the inode space. This causes afork_{ptr,size} to be nonsense. What we really ought to do here is zap the attr fork.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=e744cef206055954517648070d2b3aaa3d2515ba <c28b4b48deac17749ed1ebe4289a4ba73541ddc6, >=e744cef206055954517648070d2b3aaa3d2515ba <471e4ae43cc5f931430f7701df45ce82c8afc05d, >=e744cef206055954517648070d2b3aaa3d2515ba <4a6217e7bdf3b1cdd28799d19c175cb3bad375ec, >=e744cef206055954517648070d2b3aaa3d2515ba <6b93f0aeb8815a3ad296492e97173f9fc137340e, =6.8 | c28b4b48deac17749ed1ebe4289a4ba73541ddc6, 471e4ae43cc5f931430f7701df45ce82c8afc05d, 4a6217e7bdf3b1cdd28799d19c175cb3bad375ec, 6b93f0aeb8815a3ad296492e97173f9fc137340e |
| linux-kernel: Kernel | >=6.19.0 <7.3.2, >=6.8.0 <6.12.117, >=6.13.0 <6.18.61 | 7.3.2, 6.12.117, 6.18.61 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket