Kernel: Use After Free
CVE-2022-1043 is a high-severity use after free vulnerability in Kernel, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected Kernel versions: Fixed in kernel v5.14 rc7. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 3.83% chance of exploitation within 30 days, which is in the top 9.73% of all scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux Kernel to 5.10.61 or 5.13.13, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Kernel | Kernel | Fixed in kernel v5.14 rc7 | Not stated |
| Linux | Linux Kernel | 5.10.51 up to, but not including, 5.10.61; 5.11 up to, but not including, 5.13.13 | 5.10.61, 5.13.13 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by NVD.
Official description
A flaw was found in the Linux kernel’s io_uring implementation. This flaw allows an attacker with a local account to corrupt system memory, crash the system or escalate privileges.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.
How developers prevent this class of flaw
- Choose a language that provides automatic memory management.
- When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/torvalds/linux/commit/a30f895ad3239f45012e860d4f94c1a388b36d14Third Party Advisory
Third-party and government advisories
- access.redhat.com/security/cve/CVE-2022-1043Third Party Advisory
- bugzilla.redhat.com/show_bug.cgi?id=1997328Issue Tracking, Third Party Advisory
- zerodayinitiative.com/advisories/ZDI-22-362/Third Party Advisory, VDB Entry
Technical write-ups (may include proof of concept)
- packetstormsecurity.com/files/170834/io_uring-Same-Type-Object-Reuse-Privilege-Escalation.htmlExploit, Third Party Advisory, VDB Entry
Other vulnerabilities in Kernel
- 7.5 High severity
- 7.8 High severity
- 8.1 High severity
- 7.1 High severity
- 8.1 High severity
- 8.1 High severity
Recent Use After Free vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.