Review reviewHigh

CVE-2024-26614

Linux Linux, linux kernel, debian linux

In the Linux kernel, the following vulnerability has been resolved: tcp: make sure init the accept_queue's spinlocks once When I run syz's reproduction C program locally, it causes the following issue: pvqspinlock: lock 0xffff9d181cd5c660 has corrupted value 0x0! WARNING: CPU: 19 PID: 21160 at __pv_queued_spin_unlock_slowpath (kernel/locking/qspinlock_paravirt.h:508) Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 RIP: 0010:__pv_queued_spin_unlock_slowpath (kernel/locking/qspinlock_paravirt.h:508) Code: 73 56 3a ff 90 c3 cc cc cc cc 8b 05 bb 1f 48 01 85 c0 74 05 c3 cc cc cc cc 8b 17 48 89...

CVSS
7.8
EPSS
0.18%
7.78% percentile
CISA KEV
Not listed
Published
2024.03.12
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.18%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: tcp: make sure init the accept_queue's spinlocks once When I run syz's reproduction C program locally, it causes the following issue: pvqspinlock: lock 0xffff9d181cd5c660 has corrupted value 0x0! WARNING: CPU: 19 PID: 21160 at __pv_queued_spin_unlock_slowpath (kernel/locking/qspinlock_paravirt.h:508) Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 RIP: 0010:__pv_queued_spin_unlock_slowpath (kernel/locking/qspinlock_paravirt.h:508) Code: 73 56 3a ff 90 c3 cc cc cc cc 8b 05 bb 1f 48 01 85 c0 74 05 c3 cc cc cc cc 8b 17 48 89...

Affected product and versions

Product
Linux Linux, linux kernel, debian linux
Affected versions
>= 168a8f58059a22feb9e9a2dcc1b8053dbbbc12ef < bc99dcedd2f422d602516762b96c8ef1ae6b2882, >= 168a8f58059a22feb9e9a2dcc1b8053dbbbc12ef < d86cc6ab33b085eaef27ea88b78fc8e2375c0ef3, >= 168a8f58059a22feb9e9a2dcc1b8053dbbbc12ef < b1e0a68a0cd2a83259c444f638b417a8fffc6855, >= 168a8f58059a22feb9e9a2dcc1b8053dbbbc12ef < 168e7e599860654876c2a1102a82610285c02f02, >= 168a8f58059a22feb9e9a2dcc1b8053dbbbc12ef < 3982fe726a63fb3de6005e534e2ac8ca7e0aca2a, >= 168a8f58059a22feb9e9a2dcc1b8053dbbbc12ef < 198bc90e0e734e5f98c3d2833e8390cac3df61b2, >= 3.7, >= 3.7 < 5.10.210, >= 5.11 < 5.15.149, >= 5.16 < 6.1.76, >= 6.2 < 6.6.15, >= 6.7 < 6.7.3, 6.8, 10.0
Fixed versions
5.10.210, 5.15.149, 6.1.76, 6.6.15, 6.7.3

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel, debian linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-667
CVE-2024-26614 — Linux Linux, linux kernel, debian linux | SECUFOCUS NOW