Thursday, March 13, 2025
Homecyber securitySeven-Year-Old Linux Kernel Bug Opens Door to Remote Code Execution

Seven-Year-Old Linux Kernel Bug Opens Door to Remote Code Execution

Published on

SIEM as a Service

Follow Us on Google News

Researchers have uncovered a critical vulnerability in the Linux kernel, dating back seven years, that could allow attackers to execute remote code.

The flaw, identified in the core TCP subsystem, was introduced through a race condition in the inet_twsk_hashdance function.

This issue, now tracked as CVE-2024-36904, was patched last year after being reported by security researchers.

Technical Breakdown of the Vulnerability

The vulnerability stems from a race condition between the tcp_twsk_unique() and inet_twsk_hashdance() functions.

Specifically, the issue arises because a time-wait TCP socket’s reference counter is initialized after being inserted into a hash table and releasing a lock.

If a lookup occurs before this initialization, the object is found with a zeroed reference counter, triggering warnings and potentially leading to use-after-free scenarios.

The flaw was first noticed during routine audits of the Linux kernel source code and fuzzing tests using tools like Syzkaller.

The researchers initially aimed to reproduce another known bug but inadvertently discovered this deeper issue.

They confirmed its presence in several Linux distributions, including Red Hat Enterprise Linux derivatives and Fedora.

Exploitation Potential

While Linux kernels include protections against reference counter issues, this vulnerability bypasses those safeguards under specific conditions.

If operations on the socket follow an exact sequence, the reference counter can become unbalanced, leading to premature object release and genuine use-after-free exploitation.

This could allow attackers to execute arbitrary code within the kernel context.

Proof-of-concept exploits demonstrated that this vulnerability could be triggered under controlled conditions.

However, real-world exploitation would require precise timing and understanding of kernel internals.

The vulnerability was patched upstream in May 2024. Administrators are urged to update their systems to kernel versions containing the fix.

For Red Hat Enterprise Linux derivatives and other affected distributions, applying vendor-provided patches is critical.

Allele Security discovery underscores the importance of proactive kernel auditing and patching practices.

As vulnerabilities can persist unnoticed for years, organizations should prioritize timely updates to mitigate risks associated with legacy flaws.

The CVE-2024-36904 case highlights how even long-standing vulnerabilities can pose significant security threats if left unaddressed.

Are you from SOC/DFIR Team? - Join 500,000+ Researchers to Analyze Cyber Threats with ANY.RUN Sandbox - Try for Free

Aman Mishra
Aman Mishra
Aman Mishra is a Security and privacy Reporter covering various data breach, cyber crime, malware, & vulnerability.

Latest articles

Blind Eagle Targets Organizations with Weaponized .URL Files to Steal User Hashes

In a significant development in the cybersecurity landscape, APT-C-36, more commonly known as Blind...

INE Security Alert: Using AI-Driven Cybersecurity Training to Counter Emerging Threats

As Artificial Intelligence (AI)-powered cyber threats surge, INE Security, a global leader in cybersecurity...

Apache NiFi Vulnerability Exposes MongoDB Credentials to Attackers

A critical security vulnerability has been identified in Apache NiFi, a popular open-source data...

86,000+ Healthcare Staff Records Exposed Due to AWS S3 Misconfiguration

A non-password-protected database belonging to ESHYFT, a New Jersey-based HealthTech company, was recently discovered...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Blind Eagle Targets Organizations with Weaponized .URL Files to Steal User Hashes

In a significant development in the cybersecurity landscape, APT-C-36, more commonly known as Blind...

Apache NiFi Vulnerability Exposes MongoDB Credentials to Attackers

A critical security vulnerability has been identified in Apache NiFi, a popular open-source data...

86,000+ Healthcare Staff Records Exposed Due to AWS S3 Misconfiguration

A non-password-protected database belonging to ESHYFT, a New Jersey-based HealthTech company, was recently discovered...