MEDIUM CVSS 4.7
Published: 2026-05-28

CVE-2026-46194

linux linux_kernel Security Advisory (CVE-2026-46194)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2026-46194?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2026-46194 impacting linux linux_kernel. Evaluated with CVSS Base Score of 4.7 (MEDIUM).

Original NVD Description

Source: NIST NVD
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix node_cnt race between extent node destroy and writeback f2fs_destroy_extent_node() does not set FI_NO_EXTENT before clearing extent nodes. When called from f2fs_drop_inode() with I_SYNC set, concurrent kworker writeback can insert new extent nodes into the same extent tree, racing with the destroy and triggering f2fs_bug_on() in __destroy_extent_node(). The scenario is as follows: drop inode writeback - iput - f2fs_drop_inode // I_SYNC set - f2fs_destroy_extent_node - __destroy_extent_node - while (node_cnt) { write_lock(&et->lock) __free_extent_tree write_unlock(&et->lock) - __writeback_single_inode - f2fs_outplace_write_data - f2fs_update_read_extent_cache - __update_extent_tree_range // FI_NO_EXTENT not set, // insert new extent node } // node_cnt == 0, exit while - f2fs_bug_on(node_cnt) // node_cnt > 0 Additionally, __update_extent_tree_range() only checks FI_NO_EXTENT for EX_READ type, leaving EX_BLOCK_AGE updates completely unprotected. This patch set FI_NO_EXTENT under et->lock in __destroy_extent_node(), consistent with other callers (__update_extent_tree_range and __drop_extent_tree) and check FI_NO_EXTENT for both EX_READ and EX_BLOCK_AGE tree.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Local (AV:L)
Requires local system execution permissions
Attack Complexity
High (AC:H)
Depends on race conditions or environment
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-367

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-2026-46194 impacting linux linux_kernel.

⚡ Nuclei Detection Template (YAML) cve-2026-46194.yaml
id: cve-2026-46194

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

f2fs: fix node_cnt race between extent node destroy and writeback

f2fs_destroy_e...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2026-46194
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
    cvss-score: 4.7
    cve-id: CVE-2026-46194
    cwe-id: CWE-367
  tags: cve,cve-2026-46194,linux,linux_kernel,medium

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-2026-46194.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2026-46194
# Target: linux linux_kernel | CVSS: 4.7 (MEDIUM)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2026-46194 (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-2026-46194.sh
# Recommended Remediation & Patching Commands for CVE-2026-46194
# 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.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2026-46194 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-2026-46194?

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-2026-46194?

CVE-2026-46194 is classified with a CVSS 3.1 Base Score of 4.7 (MEDIUM). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
4.7
MEDIUM SEVERITY
CVE ID CVE-2026-46194
Weakness CWE-367
Vendor linux
Product linux_kernel
Published 2026-05-28
Vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H