CyberSecBulletin
CVE-2024-57838NVD status: Modified

Linux: Exposure of Resource to Wrong Sphere

Published Updated By the CyberSecBulletin desk

CVE-2024-57838 is a high-severity exposure of resource to wrong sphere vulnerability in Linux, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 5bb7a2c3afcf8732dc65ea49c09147b07da1d993, 1af22528fee8072b7adc007b8ca49cc4ea62689e, 473ffae3030188f1c6b80e1b3631a26b4adf7b32 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.22% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 5bb7a2c3afcf8732dc65ea49c09147b07da1d993 or 1af22528fee8072b7adc007b8ca49cc4ea62689e or 473ffae3030188f1c6b80e1b3631a26b4adf7b32 or 45c9f2b856a075a34873d00788d2e8a250c1effd, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.15.174 or 6.1.120 or 6.6.64 or 6.12.4, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxe940066089490efde86abc519593be84362f4e53 up to, but not including, 5bb7a2c3afcf8732dc65ea49c09147b07da1d993; e940066089490efde86abc519593be84362f4e53 up to, but not including, 1af22528fee8072b7adc007b8ca49cc4ea62689e; e940066089490efde86abc519593be84362f4e53 up to, but not including, 473ffae3030188f1c6b80e1b3631a26b4adf7b32; e940066089490efde86abc519593be84362f4e53 up to, but not including, 45c9f2b856a075a34873d00788d2e8a250c1effd; 5.175bb7a2c3afcf8732dc65ea49c09147b07da1d993, 1af22528fee8072b7adc007b8ca49cc4ea62689e, 473ffae3030188f1c6b80e1b3631a26b4adf7b32, 45c9f2b856a075a34873d00788d2e8a250c1effd
LinuxLinux Kernelbefore 5.15.174; 5.16 up to, but not including, 6.1.120; 6.2 up to, but not including, 6.6.64; 6.7 up to, but not including, 6.12.45.15.174, 6.1.120, 6.6.64, 6.12.4

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. Scored by NVD.

Official description

In the Linux kernel, the following vulnerability has been resolved: s390/entry: Mark IRQ entries to fix stack depot warnings The stack depot filters out everything outside of the top interrupt context as an uninteresting or irrelevant part of the stack traces. This helps with stack trace de-duplication, avoiding an explosion of saved stack traces that share the same IRQ context code path but originate from different randomly interrupted points, eventually exhausting the stack depot. Filtering uses in_irqentry_text() to identify functions within the .irqentry.text and .softirqentry.text sections, which then become the last stack trace entries being saved. While __do_softirq() is placed into the .softirqentry.text section by common code, populating .irqentry.text is architecture-specific. Currently, the .irqentry.text section on s390 is empty, which prevents stack depot filtering and de-duplication and could result in warnings like: Stack depot reached limit capacity WARNING: CPU: 0 PID: 286113 at lib/stackdepot.c:252 depot_alloc_stack+0x39a/0x3c8 with PREEMPT and KASAN enabled. Fix this by moving the IO/EXT interrupt handlers from .kprobes.text into the .irqentry.text section and updating the kprobes blacklist to include the .irqentry.text section. This is done only for asynchronous interrupts and explicitly not for program checks, which are synchronous and where the context beyond the program check is important to preserve. Despite machine checks being somewhat in between, they are extremely rare, and preserving context when possible is also of value. SVCs and Restart Interrupts are not relevant, one being always at the boundary to user space and the other being a one-time thing. IRQ entries filtering is also optionally used in ftrace function graph, where the same logic applies.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Exposure of Resource to Wrong Sphere

The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

More Exposure of Resource to Wrong Sphere vulnerabilities (CWE-668)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Exposure of Resource to Wrong Sphere vulnerabilities

Spotted an error? Tell us.