In the Linux kernel, the following vulnerability has been resolved: apparmor: fix differential encoding verification Differential encoding allows loops to be created if it is abused. To prevent this the unpack should verify that a diff-encode chain terminates. Unfortunately the differential encode verification had two bugs. 1. it conflated states that had gone through check and already been marked, with states that were currently being checked and marked. This means that loops in the current chain being verified are treated as a chain that has already been verified. 2. the order bailout on already checked states compared current chain check iterators j,k instead of using the outer loop iterator i. Meaning a step backwards in states in the current chain verification was being mistaken for moving to an already verified state. Move to a double mark scheme where already verified states get a different mark, than the current chain being kept. This enables us to also drop the backwards verification check that was the cause of the second error as any already verified state is already marked.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 031dcc8f4e84fea37dc6f78fdc7288aa7f8386c3, 031dcc8f4e84fea37dc6f78fdc7288aa7f8386c3, 031dcc8f4e84fea37dc6f78fdc7288aa7f8386c3, 031dcc8f4e84fea37dc6f78fdc7288aa7f8386c3, 031dcc8f4e84fea37dc6f78fdc7288aa7f8386c3, 4.17, 6.6.129, 6.12.76, 6.18.17, 6.19.7, 7.0-rc3 |
Downstream vendors/products affected by this vulnerability
| Vendor | Product | Source | Confidence |
|---|---|---|---|
| linux | linux | mitre_affected | 90% |
Updated affected versions, changed severity to CRITICAL, and noted that no exploit is available.
Updated description with detailed technical information, added affected version 4.17, changed severity to HIGH, updated CVSS estimate to 7.5, added CWE-20, and marked exploit availability and active exploitation as true.
Initial creation
