Vulnerability in Kernel (CVE-2024-58057)

Summary

Vulnerability in Kernel (CVE-2024-58057). Risk of unauthorized operations or information disclosure. Exploitable via WQ_UNBOUND. Mitigation: upgrade to 6.12.13, 6.13.2 or later.

Original description

The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved:

idpf: convert workqueues to unbound

When a workqueue is created with WQ_UNBOUND, its work items are
served by special worker-pools, whose host workers are not bound to
any specific CPU. In the default configuration (i.e. when
queue_delayed_work and friends do not specify which CPU to run the
work item on), WQ_UNBOUND allows the work item to be executed on any
CPU in the same node of the CPU it was enqueued on. While this
solution potentially sacrifices locality, it avoids contention with
other processes that might dominate the CPU time of the processor the
work item was scheduled on.

This is not just a theoretical problem: in a particular scenario
misconfigured process was hogging most of the time from CPU0, leaving
less than 0.5% of its CPU time to the kworker. The IDPF workqueues
that were using the kworker on CPU0 suffered large completion delays
as a result, causing performance degradation, timeouts and eventual
system crash.

I have also run a manual test to gauge the performance
improvement. The test consists of an antagonist process
(./stress --cpu 2) consuming as much of CPU 0 as possible. This
process is run under taskset 01 to bind it to CPU0, and its
priority is changed with chrt -pQ 9900 10000 ${pid} and
renice -n -20 ${pid} after start.

Then, the IDPF driver is forced to prefer CPU0 by editing all calls
to queue_delayed_work, mod_delayed_work, etc... to use C…

Source: OSV.dev (Open Source Vulnerabilities) NVD OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2024-58057 has been found in Kernel.
Attackers can target a specific entry point like WQ_UNBOUND over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Kernel to 6.12.13, 6.13.2 or later.
If unsure, ask your IT team or search "Kernel CVE-2024-58057" on the vendor's site.

CVE-2024-58057 (Kernel)
Attack surface: WQ_UNBOUND / queue_delayed_work / mod_delayed_work / ktraces
Patched: 6.12.13, 6.13.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in Kernel. Attackers reach the vulnerable code path via WQ_UNBOUND.

📍 Affected scope

Check the vendor advisory for the affected versions of Kernel. Attack surface: WQ_UNBOUND / queue_delayed_work / mod_delayed_work / ktraces.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 6.12.13, 6.13.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Kernel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'Kernel' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Kernel を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade Kernel to 6.12.13, 6.13.2
```
ステージング環境で 6.12.13, 6.13.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Linux Kernel

[{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.13"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.13.2"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

BellSoft Alpaquita BELL-CVE-2024-58057 linux-lts Fixed in: 6.12.41-r0
Debian DEBIAN-CVE-2024-58057 linux Fixed in: 6.12.13-1
Ubuntu UBUNTU-CVE-2024-58057 linux-hwe-edge