Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-42240: x86/bhi: Avoid warning in #DB handler due to BHI mitigation

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 08518d48e5b744620524f0acd7c26c19bda7f513, 5.15.163, 6.1.100.

Low priority for now. Upgrade to Linux Linux 08518d48e5b744620524f0acd7c26c19bda7f513, 5.15.163, 6.1.100 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: x86/bhi: Avoid warning in #DB handler due to BHI mitigation When BHI mitigation is enabled, if SYSENTER is invoked with the TF flag set then entry_SYSENTER_compat() uses CLEAR_BRANCH_HISTORY and calls the clear_bhb_loop() before the TF flag is cleared. This causes the #DB handler (exc_debug_kernel()) to issue a warning because single-step is used outside the entry_SYSENTER_compat() function. To address this issue, entry_SYSENTER_compat() should use CLEAR_BRANCH_HISTORY after making sure the TF flag is cleared. The problem can be reproduced with the following sequence: $ cat sysenter_step.c int main() { asm("pushf; pop %ax; bts $8,%ax; push %ax; popf; sysenter"); } $ gcc -o sysenter_step sysenter_step.c $ ./sysenter_step Segmentation fault (core dumped) The program is expected to crash, and the #DB handler will issue a warning. Kernel log: WARNING: CPU: 27 PID: 7000 at arch/x86/kernel/traps.c:1009 exc_debug_kernel+0xd2/0x160 ... RIP: 0010:exc_debug_kernel+0xd2/0x160 ... Call Trace: <#DB> ? show_regs+0x68/0x80 ? __warn+0x8c/0x140 ? exc_debug_kernel+0xd2/0x160 ? report_bug+0x175/0x1a0 ? handle_bug+0x44/0x90 ? exc_invalid_op+0x1c/0x70 ? asm_exc_invalid_op+0x1f/0x30 ? exc_debug_kernel+0xd2/0x160 exc_debug+0x43/0x50 asm_exc_debug+0x1e/0x40 RIP: 0010:clear_bhb_loop+0x0/0xb0 ... </#DB> <TASK> ? entry_SYSENTER_compat_after_hwframe+0x6e/0x8d </TASK> [ bp: Massage commit message. ]

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Aug 7, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 12th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-42240

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.15.163 and later · before 6.1.100
  • linux linux kernel6.2 and later · before 6.6.41
  • linux linux kernel6.7 and later · before 6.9.10

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 8f51637712e4da5be410a1666f8aee0d86eef898, 6.9affected
    • bd53ec80f21839cfd4d852a6088279d602d67e5b and later · before db56615e96c439e13783d7715330e824b4fd4b84affected · git
    • 07dbb10f153f483e8249acebdffedf922e2ec2e1 and later · before a765679defe1dc1b8fa01928a6ad6361e72a1364affected · git
    • eb36b0dce2138581bc6b5e39d0273cb4c96ded81 and later · before dae3543db8f0cf8ac1a198c3bb4b6e3c24d576cfaffected · git
    • 7390db8aea0d64e9deb28b8e1ce716f5020c7ee5 and later · before 08518d48e5b744620524f0acd7c26c19bda7f513affected · git
    • 7390db8aea0d64e9deb28b8e1ce716f5020c7ee5 and later · before ac8b270b61d48fcc61f052097777e3b5e11591e0affected · git
    • 5.15.154 and later · before 5.15.163affected · semver
    • 6.1.85 and later · before 6.1.100affected · semver
    • 6.6.26 and later · before 6.6.41affected · semver
    • 6.8.5 and later · before 6.9affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.106-16.1.106-1
Debian:13linuxbefore 6.9.10-16.9.10-1
Red Hat:rhel_eus:9.2::appstreambpftool-debuginfobefore 0:7.0.0-284.95.1.el9_20:7.0.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debug-develbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debuginfobefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-develbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debug-debuginfobefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debug-develbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfobefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-develbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-devel-matchedbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-docbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-tools-debuginfobefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-zfcpdump-develbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-zfcpdump-devel-matchedbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2

+54

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-42237Aug 7, 2024 · firmware: cs_dsp: Validate payload length before processing block
    22Monitor
  • ← EarlierCVE-2024-42238Aug 7, 2024 · firmware: cs_dsp: Return error if block header overflows file
    22Monitor
  • Later →CVE-2024-42242Aug 7, 2024 · mmc: sdhci: Fix max_seg_size for 64KiB PAGE_SIZE
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux08518d48e5b744620524f0acd7c26c19bda7f513Vendor (CNA)
Linux Linux5.15.163Vendor (CNA)
Linux Linux6.1.100Vendor (CNA)
Linux Linux6.6.41Vendor (CNA)
Linux Linux6.9Vendor (CNA)
Linux Linuxa765679defe1dc1b8fa01928a6ad6361e72a1364Vendor (CNA)
Linux Linuxac8b270b61d48fcc61f052097777e3b5e11591e0Vendor (CNA)
Linux Linuxdae3543db8f0cf8ac1a198c3bb4b6e3c24d576cfVendor (CNA)
Linux Linuxdb56615e96c439e13783d7715330e824b4fd4b84Vendor (CNA)
debian:linux6.1.106-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.0.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-2703298 days apartf2fs: fix to avoid potential panic during recovery
    25Monitor
  • CVE-2022-48635101 days apartfsdax: Fix infinite loop in dax_iomap_rw()
    24Monitor
  • CVE-2024-422460 days apartnet, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket
    22Monitor
  • CVE-2024-410889 days apartcan: mcp251xfd: fix infinite loop when xmit fails
    22Monitor
  • CVE-2024-4382810 days apartext4: fix infinite loop when replaying fast_commit
    22Monitor
  • CVE-2022-4886222 days apartvhost: fix hung thread due to erroneous iotlb entries
    22Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records