SECUFOCUSNOW
Home›CVE index›CVE-2021-47598
Review reviewHigh

CVE-2021-47598

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: sch_cake: do not call cake_destroy() from cake_init() qdiscs are not supposed to call their own destroy() method from init(), because core stack already does that. syzbot was able to trigger use after free: DEBUG_LOCKS_WARN_ON(lock->magic != lock) WARNING: CPU: 0 PID: 21902 at kernel/locking/mutex.c:586 __mutex_lock_common kernel/locking/mutex.c:586 [inline] WARNING: CPU: 0 PID: 21902 at kernel/locking/mutex.c:586 __mutex_lock+0x9ec/0x12f0 kernel/locking/mutex.c:740 Modules linked in: CPU: 0 PID: 21902 Comm: syz-executor189...

CVSS
7.8
EPSS
0.26%
17.0% percentile
CISA KEV
Not listed
Published
2024.06.20
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

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

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: sch_cake: do not call cake_destroy() from cake_init() qdiscs are not supposed to call their own destroy() method from init(), because core stack already does that. syzbot was able to trigger use after free: DEBUG_LOCKS_WARN_ON(lock->magic != lock) WARNING: CPU: 0 PID: 21902 at kernel/locking/mutex.c:586 __mutex_lock_common kernel/locking/mutex.c:586 [inline] WARNING: CPU: 0 PID: 21902 at kernel/locking/mutex.c:586 __mutex_lock+0x9ec/0x12f0 kernel/locking/mutex.c:740 Modules linked in: CPU: 0 PID: 21902 Comm: syz-executor189...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 046f6fd5daefac7f5abdafb436b30f63bc7c602b < 4e388232e630ebe4f94b4a0715ec98c0e2b314a3, >= 046f6fd5daefac7f5abdafb436b30f63bc7c602b < 0d80462fbdcafd536dcad7569e65d3d14a7e9f2f, >= 046f6fd5daefac7f5abdafb436b30f63bc7c602b < 20ad1ef02f9ad5e1dda9eeb113e4c158b4806986, >= 046f6fd5daefac7f5abdafb436b30f63bc7c602b < f6deae2e2d83bd267e1986f5d71d8c458e18fd99, >= 046f6fd5daefac7f5abdafb436b30f63bc7c602b < ab443c53916730862cec202078d36fd4008bea79, >= 4.19, >= 4.19 < 4.19.222, >= 4.20 < 5.4.168, >= 5.5 < 5.10.88, >= 5.11 < 5.15.11
Fixed versions
4.19.222, 5.4.168, 5.10.88, 5.15.11

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel 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-416