CVE-2022-49344

af_unix: Fix a data-race in unix_dgram_peer_wake_me().

MEDIUM

4.7

CVSS Score

Published: February 26, 2025 at 02:11 AM UTC

Updated: June 17, 2026 at 05:17 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM4.7

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: af_unix: Fix a data-race in unix_dgram_peer_wake_me(). unix_dgram_poll() calls unix_dgram_peer_wake_me() without `other`'s lock held and check if its receive queue is full. Here we need to use unix_recvq_full_lockless() instead of unix_recvq_full(), otherwise KCSAN will report a data-race.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v ≥ 2.6.32.70v ≥ 3.10.95v ≥ 3.12.52v ≥ 3.14.59v ≥ 3.18.26v ≥ 3.2.75v ≥ 3.4.111v ≥ 4.1.15v ≥ 4.2.8v ≥ 4.3.32.6.32.70 ≤ v < 2.6.333.10.95 ≤ v < 3.113.12.52 ≤ v < 3.133.14.59 ≤ v < 3.153.18.26 ≤ v < 3.193.2.75 ≤ v < 3.33.4.111 ≤ v < 3.54.1.15 ≤ v < 4.24.2.8 ≤ v < 4.34.20 ≤ v < 5.4.1984.3.3 ≤ v < 4.19.2474.3.3 ≤ v < 4.44.4 ≤ v < 4.19.2474.4 ≤ v < 5.10.1224.4 ≤ v < 5.15.474.4 ≤ v < 5.17.154.4 ≤ v < 5.18.44.4 ≤ v < 5.194.4 ≤ v < 5.4.1985.11 ≤ v < 5.15.475.16 ≤ v < 5.17.155.18 ≤ v < 5.18.45.5 ≤ v < 5.10.1222.6.32.70 3.10.95 3.12.52 3.14.59 3.18.26 3.2.75 3.4.111 4.1.15 4.2.8 4.3.3 5.19 rc158a6a46a036ce81a2a8ecaa6fc1537c894349e3f5c77e26862ce604edea05b3442ed765e9756fe0f60bc010667ef06e0fb08d5ec599c0977adc2ac7272032798034d921ed565e3bf8dfdc3098f6473e27d267278a9ece963d77eefec61630223fce08c6c9964b4c4ee925b2910723e509abd7241cff1ef849d054f57adc981a5f503d5eb9b259aa450b90dc5a3b0f6e8a21ef02f69a15abac440572d8cde8c2abad967fdd8ecbdd171f5f243657be033d2d081a7da8db0830a2ce63f628150307a01a315f5081202ec54d5ae9d298abf01c273233de9f2bc25d80475

Vendor states this is fixed in 556720013c36c193d9cbfb06e7b33e51f0c39fbf (fixed)

Vendor states this is fixed in 662a80946ce13633ae90a55379f1346c10f0c432 (fixed)

Vendor states this is fixed in 71e8bfc7f838cabc60cba24e09ca84c4f8321ab2 (fixed)

Vendor states this is fixed in 8801eb3ccd2e4e3b1a01449383e3321ae6dbd9d6 (fixed)

Vendor states this is fixed in 95f0ba806277733bf6024e23e27e1be773701cca (fixed)

Vendor states this is fixed in c61848500a3fd6867dfa4834b8c7f97133eceb9f (fixed)

Vendor states this is fixed in c926ae58f24f7bd55aa2ea4add9f952032507913 (fixed)

Affected range stops below 2.6.33, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.11, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.13, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.15, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.19, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.5, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 4.19.247 (unaffected)

Affected range stops below 4.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.3, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 4.4 (unaffected)

Vendor states this is fixed in 5.10.122 (unaffected)

Vendor states this is fixed in 5.15.47 (unaffected)

Vendor states this is fixed in 5.17.15 (unaffected)

Vendor states this is fixed in 5.18.4 (unaffected)

Vendor states this is fixed in 5.19 (unaffected)

Vendor states this is fixed in 5.4.198 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references