CyberSecBulletin
CVE-2022-3176NVD status: Modified

Kernel: Use After Free

CVE-2022-3176 is a high-severity use after free vulnerability in Kernel from Linux, with a CVSS 3.1 base score of 7.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. The record lists version fc78b2fc21f10c4c9c4d5d659a685710ffa63659 as the first without the flaw, so updating Kernel to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.3% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Kernel to fc78b2fc21f10c4c9c4d5d659a685710ffa63659 or a later version.
  2. Update Linux Kernel to 5.4.212 or 5.10.141 or 5.15.65 or 5.17, whichever matches your release line, or a later version.
  3. Read the advisory on git.kernel.org for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxKernelbefore fc78b2fc21f10c4c9c4d5d659a685710ffa63659fc78b2fc21f10c4c9c4d5d659a685710ffa63659
LinuxLinux Kernel5.1 up to, but not including, 5.4.212; 5.5 up to, but not including, 5.10.141; 5.11 up to, but not including, 5.15.65; 5.16 up to, but not including, 5.175.4.212, 5.10.141, 5.15.65, 5.17
DebianDebian Linux10.0; 11.0Not stated

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
UnchangedImpact stays within the vulnerable component.
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:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighCNA (google.com)
CVSS 3.17.8HighNVD

Official description

There exists a use-after-free in io_uring in the Linux kernel. Signalfd_poll() and binder_poll() use a waitqueue whose lifetime is the current task. It will send a POLLFREE notification to all waiters before the queue is freed. Unfortunately, the io_uring poll doesn't handle POLLFREE. This allows a use-after-free to occur if a signalfd or binder fd is polled with io_uring poll, and the waitqueue gets freed. We recommend upgrading past commit fc78b2fc21f10c4c9c4d5d659a685710ffa63659

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.

More Use After Free vulnerabilities (CWE-416)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in Kernel

All Kernel vulnerabilities

Recent Use After Free vulnerabilities

Spotted an error? Tell us.