How to scan and detect CVE-2024-57976 using Nuclei?

CyberVault provides a ready Nuclei YAML detection template for CVE-2024-57976 impacting linux linux_kernel. Execute it via: nuclei -t cve-2024-57976.yaml -u .

Where can I find Proof of Concept (PoC) exploit code for CVE-2024-57976?

CyberVault provides an educational verification probe and PoC Python script for CVE-2024-57976 to audit exposed linux linux_kernel services.

How do I fix CVE-2024-57976 vulnerability in linux linux_kernel?

Review vendor security advisories and upgrade linux linux_kernel to the latest patched release. Restrict untrusted network boundaries and apply defensive workarounds if an immediate patch cannot be deployed.

Is there a public exploit or PoC available for CVE-2024-57976?

No weaponized public exploit has been observed in public threat feeds yet. Continuous surveillance is active.

What is the severity and CVSS score of CVE-2024-57976?

CVE-2024-57976 is evaluated as HIGH with an authentic CVSS base score of 7.8.

HIGH CVSS 7.8

Published: 2025-02-27

CVE-2024-57976

linux linux_kernel Security Advisory (CVE-2024-57976)

↗ Official NIST NVD Record

Seeking technical exploit breakdowns or verified PoC code for CVE-2024-57976?

🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2024-57976 impacting linux linux_kernel. Evaluated with CVSS Base Score of 7.8 (HIGH).

Original NVD Description

Source: NIST NVD

In the Linux kernel, the following vulnerability has been resolved: btrfs: do proper folio cleanup when cow_file_range() failed [BUG] When testing with COW fixup marked as BUG_ON() (this is involved with the new pin_user_pages*() change, which should not result new out-of-band dirty pages), I hit a crash triggered by the BUG_ON() from hitting COW fixup path. This BUG_ON() happens just after a failed btrfs_run_delalloc_range(): BTRFS error (device dm-2): failed to run delalloc range, root 348 ino 405 folio 65536 submit_bitmap 6-15 start 90112 len 106496: -28 ------------[ cut here ]------------ kernel BUG at fs/btrfs/extent_io.c:1444! Internal error: Oops - BUG: 00000000f2000800 [#1] SMP CPU: 0 UID: 0 PID: 434621 Comm: kworker/u24:8 Tainted: G OE 6.12.0-rc7-custom+ #86 Hardware name: QEMU KVM Virtual Machine, BIOS unknown 2/2/2022 Workqueue: events_unbound btrfs_async_reclaim_data_space [btrfs] pc : extent_writepage_io+0x2d4/0x308 [btrfs] lr : extent_writepage_io+0x2d4/0x308 [btrfs] Call trace: extent_writepage_io+0x2d4/0x308 [btrfs] extent_writepage+0x218/0x330 [btrfs] extent_write_cache_pages+0x1d4/0x4b0 [btrfs] btrfs_writepages+0x94/0x150 [btrfs] do_writepages+0x74/0x190 filemap_fdatawrite_wbc+0x88/0xc8 start_delalloc_inodes+0x180/0x3b0 [btrfs] btrfs_start_delalloc_roots+0x174/0x280 [btrfs] shrink_delalloc+0x114/0x280 [btrfs] flush_space+0x250/0x2f8 [btrfs] btrfs_async_reclaim_data_space+0x180/0x228 [btrfs] process_one_work+0x164/0x408 worker_thread+0x25c/0x388 kthread+0x100/0x118 ret_from_fork+0x10/0x20 Code: aa1403e1 9402f3ef aa1403e0 9402f36f (d4210000) ---[ end trace 0000000000000000 ]--- [CAUSE] That failure is mostly from cow_file_range(), where we can hit -ENOSPC. Although the -ENOSPC is already a bug related to our space reservation code, let's just focus on the error handling. For example, we have the following dirty range [0, 64K) of an inode, with 4K sector size and 4K page size: 0 16K 32K 48K 64K |///////////////////////////////////////| |#######################################| Where |///| means page are still dirty, and |###| means the extent io tree has EXTENT_DELALLOC flag. - Enter extent_writepage() for page 0 - Enter btrfs_run_delalloc_range() for range [0, 64K) - Enter cow_file_range() for range [0, 64K) - Function btrfs_reserve_extent() only reserved one 16K extent So we created extent map and ordered extent for range [0, 16K) 0 16K 32K 48K 64K |////////|//////////////////////////////| |<- OE ->|##############################| And range [0, 16K) has its delalloc flag cleared. But since we haven't yet submit any bio, involved 4 pages are still dirty. - Function btrfs_reserve_extent() returns with -ENOSPC Now we have to run error cleanup, which will clear all EXTENT_DELALLOC* flags and clear the dirty flags for the remaining ranges: 0 16K 32K 48K 64K |////////| | | | | Note that range [0, 16K) still has its pages dirty. - Some time later, writeback is triggered again for the range [0, 16K) since the page range still has dirty flags. - btrfs_run_delalloc_range() will do nothing because there is no EXTENT_DELALLOC flag. - extent_writepage_io() finds page 0 has no ordered flag Which falls into the COW fixup path, triggering the BUG_ON(). Unfortunately this error handling bug dates back to the introduction of btrfs. Thankfully with the abuse of COW fixup, at least it won't crash the kernel. [FIX] Instead of immediately unlocking the extent and folios, we keep the extent and folios locked until either erroring out or the whole delalloc range finished. When the whole delalloc range finished without error, we just unlock the whole range with PAGE_SET_ORDERED (and PAGE_UNLOCK for !keep_locked cases) ---truncated---

📊 CVSS v3.1 Metric Breakdown

Attack Vector

Local (AV:L)

Requires local system execution permissions

Attack Complexity

Low (AC:L)

No specialized conditions required

Privileges Required

Low (PR:L)

Standard user access required

User Interaction

None (UI:N)

Zero human interaction required

Scope

Unchanged (S:U)

Confined to same security context

Confidentiality

None (C:N)

No data confidentiality impact

Integrity

None (I:N)

No system modification impact

Availability

High (A:H)

Total denial of service or shutdown

🎯 Affected Versions Matrix

Affected Product	linux / linux_kernel
Affected Versions	*
Weakness Enumeration	CWE-459

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2024-57976 impacting linux linux_kernel.

⚡ Nuclei Detection Template (YAML) cve-2024-57976.yaml

id: cve-2024-57976

info:
  name: linux linux_kernel - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: high
  description: |
    Automated signature & scanner for CVE-2024-57976 affecting linux linux_kernel.
    Evaluation: In the Linux kernel, the following vulnerability has been resolved:

btrfs: do proper folio cleanup when cow_file_range() failed

[BUG]
When testing w...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2024-57976
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
    cvss-score: 7.8
    cve-id: CVE-2024-57976
    cwe-id: CWE-459
  tags: cve,cve-2024-57976,linux,linux_kernel,high

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "linux_kernel"
        part: body

🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2024-57976.py

# Proof-of-Concept Exploit & Verification Probe for CVE-2024-57976
# Target: linux linux_kernel | CVSS: 7.8 (HIGH)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2024-57976 (linux linux_kernel)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against linux linux_kernel scope (*).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)

🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2024-57976.sh

# Recommended Remediation & Patching Commands for CVE-2024-57976
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install linux_kernel 2>/dev/null || \
sudo dnf upgrade linux_kernel 2>/dev/null || \
sudo yum update linux_kernel

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i linux_kernel 2>/dev/null || rpm -qa | grep -i linux_kernel

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
Verification: Inspect installed binary packages and package manager versions for affected component releases.
Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.

⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

🔗 Verified Technical References

Authorities

No records filed in this category.

Distributions

No records filed in this category.

Technical Analysis

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2024-57976 in linux linux_kernel?

Review vendor-specific security notices and update linux linux_kernel packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2024-57976?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2024-57976?

CVE-2024-57976 is classified with a CVSS 3.1 Base Score of 7.8 (HIGH). Check the metric breakdown above for attack vector requirements.

Risk Snapshot

7.8

HIGH SEVERITY

CVE ID CVE-2024-57976

Weakness CWE-459

Vendor linux

Product linux_kernel

Published 2025-02-27

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

← Return to CVE Catalog