DEBIAN-CVE-2024-42300

Source
https://security-tracker.debian.org/tracker/CVE-2024-42300
Import Source
https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2024-42300.json
JSON Data
https://api.osv.dev/v1/vulns/DEBIAN-CVE-2024-42300
Upstream
Published
2024-08-17T09:15:10.360Z
Modified
2025-11-19T02:04:29.902155Z
Severity
  • 4.7 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
Summary
[none]
Details

In the Linux kernel, the following vulnerability has been resolved: erofs: fix race in zerofsgetgbuf() In zerofsgetgbuf(), the current task may be migrated to another CPU between z_erofs_gbuf_id() and spin_lock(&gbuf->lock). Therefore, zerofsputgbuf() will trigger the following issue which was found by stress test: <2>[772156.434168] kernel BUG at fs/erofs/zutil.c:58! .. <4>[772156.435007] <4>[772156.439237] CPU: 0 PID: 3078 Comm: stress Kdump: loaded Tainted: G E 6.10.0-rc7+ #2 <4>[772156.439239] Hardware name: Alibaba Cloud Alibaba Cloud ECS, BIOS 1.0.0 01/01/2017 <4>[772156.439241] pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--) <4>[772156.439243] pc : zerofsputgbuf+0x64/0x70 [erofs] <4>[772156.439252] lr : zerofslz4decompress+0x600/0x6a0 [erofs] .. <6>[772156.445958] stress (3127): dropcaches: 1 <4>[772156.446120] Call trace: <4>[772156.446121] zerofsputgbuf+0x64/0x70 [erofs] <4>[772156.446761] zerofslz4decompress+0x600/0x6a0 [erofs] <4>[772156.446897] zerofsdecompressqueue+0x740/0xa10 [erofs] <4>[772156.447036] zerofsrunqueue+0x428/0x8c0 [erofs] <4>[772156.447160] zerofs_readahead+0x224/0x390 [erofs] ..

References

Affected packages

Debian:13 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
6.10.3-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:14 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
6.10.3-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}