CyberSecBulletin
CVE-2022-1048NVD status: Modified

kernel: Concurrent Execution using Shared Resource with Improper Synchronization

CVE-2022-1048 is a high-severity concurrent execution using shared resource with improper synchronization vulnerability in kernel, with a CVSS 3.1 base score of 7.0 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: Linux kernel 5.17-rc9. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.24% 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 Linux Kernel to 4.14.279 or 4.19.243 or 5.4.193 or 5.10.109, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
KernelkernelLinux kernel 5.17-rc9Not stated
LinuxLinux Kernel2.6.12 up to, but not including, 4.14.279; 4.15 up to, but not including, 4.19.243; 4.20 up to, but not including, 5.4.193; 5.5 up to, but not including, 5.10.109; 5.11 up to, but not including, 5.15.32; 5.16 up to, but not including, 5.16.18; 5.174.14.279, 4.19.243, 5.4.193, 5.10.109, 5.15.32, 5.16.18
Red HatEnterprise Linux8.0Not stated
DebianDebian Linux10.0; 11.0Not stated
NetAppH300s FirmwareNot specified in the recordNot stated
NetAppH500s FirmwareNot specified in the recordNot stated
NetAppH700s FirmwareNot specified in the recordNot stated
NetAppH410s FirmwareNot specified in the recordNot stated
NetAppH300e FirmwareNot specified in the recordNot stated
NetAppH500e FirmwareNot specified in the recordNot stated
NetAppH700e FirmwareNot specified in the recordNot stated
NetAppH410c FirmwareNot specified in the recordNot 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
HighSuccess depends on conditions outside the attacker's control.
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:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.0HighNVD
CVSS 2.06.9MediumNVD

Official description

A use-after-free flaw was found in the Linux kernel’s sound subsystem in the way a user triggers concurrent calls of PCM hw_params. The hw_free ioctls or similar race condition happens inside ALSA PCM for other ioctls. This flaw allows a local user to crash or potentially escalate their privileges on the system.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Concurrent Execution using Shared Resource with Improper Synchronization

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

How developers prevent this class of flaw

  • In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
  • Use thread-safe capabilities such as the data access abstraction in Spring.
  • Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring. Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).

More Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities (CWE-362)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in kernel

All kernel vulnerabilities

Recent Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities

Spotted an error? Tell us.