Menu

Star on GitHub · 3.2k

CVE-2025-40279

In the Linux kernel, the following vulnerability has been resolved: net: sched: act_connmark: initialize struct tc_ife to fix kernel leak In tcf_connmark_dump(), the variable 'opt' was partially…

Published Dec 6, 2025EPSS 0.20%

Overview

CVE-2025-40279 is a known-severity vulnerability. It was published on December 6, 2025.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

net: sched: act_connmark: initialize struct tc_ife to fix kernel leak

In tcf_connmark_dump(), the variable 'opt' was partially initialized using a

designatied initializer. While the padding bytes are reamined

uninitialized. nla_put() copies the entire structure into a

netlink message, these uninitialized bytes leaked to userspace.

Initialize the structure with memset before assigning its fields

to ensure all members and padding are cleared prior to beign copied.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-40279?

CVE-2025-40279 is a known-severity vulnerability. It was published on December 6, 2025.

How severe is CVE-2025-40279?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2025-40279?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-40279?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-40279 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.