Overview
About vulnerability
In the Linux kernel, the following vulnerability has been resolved:
apparmor: fix race between freeing data and fs accessing it
AppArmor was putting the reference to i_private data on its end after removing the original entry from the file system. However the inode can aand does live beyond that point and it is possible that some of the fs call back functions will be invoked after the reference has been put, which results in a race between freeing the data and accessing it through the fs.
While the rawdata/loaddata is the most likely candidate to fail the race, as it has the fewest references. If properly crafted it might be possible to trigger a race for the other types stored in i_private.
Fix this by moving the put of i_private referenced data to the correct place which is during inode eviction.
Details
- Affected product:
- AlmaLinux 9.2 ESU , Amazon Linux 2 ELS , CentOS 8.4 ELS , CentOS 8.5 ELS , CentOS Stream 8 ELS , Debian 10 ELS , Oracle Linux 7 ELS , TuxCare 9.6 ESU , Ubuntu 16.04 ELS , Ubuntu 18.04 ELS , Ubuntu 20.04 ELS
- Affected packages:
- kernel @ 5.14.0 (+10 more)
Fixes
KernelCare state
Live-patch status from KernelCare for each operating system.
| Operating system | Status | Covered kernels |
|---|---|---|
| Debian 11 | Planned | — |
| Debian 12 | Planned | — |
| Debian 13 | Ready For Release | — |
| Ubuntu 16.04 AWS HWE ESM | Planned | — |
| Ubuntu 16.04 GCP ESM | Planned | — |
| Ubuntu 16.04 HWE ESM | Planned | — |
| Ubuntu 18.04 | Planned | — |
| Ubuntu 18.04 AWS | Planned | — |
| Ubuntu 18.04 Azure | Planned | — |
| Ubuntu 18.04 GCP | Planned | — |
| Ubuntu 20.04 | Planned | — |