CVE-2024-49980 Vulnerability Analysis & Exploit Details

CVE-2024-49980
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2024-49980 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2024-49980 Details

Status: Analyzed

Last updated: 🕝 31 Oct 2024, 14:58 UTC
Originally published on: 🕕 21 Oct 2024, 18:15 UTC

Time between publication and last update: 9 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2024-49980 Vulnerability Summary

CVE-2024-49980: In the Linux kernel, the following vulnerability has been resolved: vrf: revert "vrf: Remove unnecessary RCU-bh critical section" This reverts commit 504fc6f4f7f681d2a03aa5f68aad549d90eab853. dev_queue_xmit_nit is expected to be called with BH disabled. __dev_queue_xmit has the following: /* Disable soft irqs for various locks below. Also * stops preemption for RCU. */ rcu_read_lock_bh(); VRF must follow this invariant. The referenced commit removed this protection. Which triggered a lockdep warning: ================================ WARNING: inconsistent lock state 6.11.0 #1 Tainted: G W -------------------------------- inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W} usage. btserver/134819 [HC0[0]:SC0[0]:HE1:SE1] takes: ffff8882da30c118 (rlock-AF_PACKET){+.?.}-{2:2}, at: tpacket_rcv+0x863/0x3b30 {IN-SOFTIRQ-W} state was registered at: lock_acquire+0x19a/0x4f0 _raw_spin_lock+0x27/0x40 packet_rcv+0xa33/0x1320 __netif_receive_skb_core.constprop.0+0xcb0/0x3a90 __netif_receive_skb_list_core+0x2c9/0x890 netif_receive_skb_list_internal+0x610/0xcc0 [...] other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(rlock-AF_PACKET); <Interrupt> lock(rlock-AF_PACKET); *** DEADLOCK *** Call Trace: <TASK> dump_stack_lvl+0x73/0xa0 mark_lock+0x102e/0x16b0 __lock_acquire+0x9ae/0x6170 lock_acquire+0x19a/0x4f0 _raw_spin_lock+0x27/0x40 tpacket_rcv+0x863/0x3b30 dev_queue_xmit_nit+0x709/0xa40 vrf_finish_direct+0x26e/0x340 [vrf] vrf_l3_out+0x5f4/0xe80 [vrf] __ip_local_out+0x51e/0x7a0 [...]

Assessing the Risk of CVE-2024-49980

Access Complexity Graph

The exploitability of CVE-2024-49980 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2024-49980

CVE-2024-49980 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2024-49980, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2024-49980, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2024-49980 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2024-49980 poses no threat to data integrity.
  • Availability: High
    CVE-2024-49980 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.042% (probability of exploit)

EPSS Percentile: 5.02% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 94.98% of others.

CVE-2024-49980 References

External References

CWE Common Weakness Enumeration

CWE-667

CAPEC Common Attack Pattern Enumeration and Classification

  • Forced Deadlock CAPEC-25 The adversary triggers and exploits a deadlock condition in the target software to cause a denial of service. A deadlock can occur when two or more competing actions are waiting for each other to finish, and thus neither ever does. Deadlock conditions can be difficult to detect.
  • Leveraging Race Conditions CAPEC-26 The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.
  • Leveraging Race Conditions via Symbolic Links CAPEC-27 This attack leverages the use of symbolic links (Symlinks) in order to write to sensitive files. An attacker can create a Symlink link to a target file not otherwise accessible to them. When the privileged program tries to create a temporary file with the same name as the Symlink link, it will actually write to the target file pointed to by the attackers' Symlink link. If the attacker can insert malicious content in the temporary file they will be writing to the sensitive file by using the Symlink. The race occurs because the system checks if the temporary file exists, then creates the file. The attacker would typically create the Symlink during the interval between the check and the creation of the temporary file.

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:6.6:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.14:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.15:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.15:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.16:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.16:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.17:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.17:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.18:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.18:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.19:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.19:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.20:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.20:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.24:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.24:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.26:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.26:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.29:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.29:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.30:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.30:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.32:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.32:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.33:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.33:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.34:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.34:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.35:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.35:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.36:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.36:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.37:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.37:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.38:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.38:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.39:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.39:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.40:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.40:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.41:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.41:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.42:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.42:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.43:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.43:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.44:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.44:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.46:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.46:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.47:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.47:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.48:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.48:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.49:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.49:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.50:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.50:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.51:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.51:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:rc8:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:rc8:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-49980: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...
  • CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
  • CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...