Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-1999-0403: A bug in Cyrix CPUs on Linux allows local users to perform a denial of service.

0
Medium
VulnerabilityCVE-1999-0403cve-1999-0403denial of service
Published: Mon Feb 01 1999 (02/01/1999, 05:00:00 UTC)
Source: NVD
Vendor/Project: cyrix
Product: linux

Description

A bug in Cyrix CPUs on Linux allows local users to perform a denial of service.

AI-Powered Analysis

AILast updated: 07/01/2025, 19:56:30 UTC

Technical Analysis

CVE-1999-0403 is a vulnerability identified in Cyrix CPUs running Linux operating systems. The issue stems from a hardware bug in Cyrix processors that can be triggered by local users to cause a denial of service (DoS) condition. Specifically, the flaw allows a local attacker to disrupt system availability by exploiting the CPU's faulty behavior under certain conditions, leading to system crashes or hangs. Since this vulnerability is rooted in the CPU hardware design rather than software, no software patch is available to remediate the issue. The vulnerability does not affect confidentiality or integrity but solely impacts availability. The CVSS score assigned is 5.0 (medium severity), with the vector indicating that the attack requires local access (AV:N - Network not required), has low attack complexity (AC:L), no authentication required (Au:N), and impacts availability only (A:P). There are no known exploits in the wild, and the vulnerability dates back to 1999, reflecting older hardware and Linux kernel versions. Modern systems and CPUs are unlikely to be affected, as Cyrix CPUs are obsolete and no longer in widespread use. However, legacy systems running Linux on Cyrix processors remain vulnerable to local DoS attacks due to this hardware bug.

Potential Impact

For European organizations, the impact of CVE-1999-0403 is limited primarily to legacy environments still operating on Cyrix CPUs with Linux. In such cases, a local attacker with access to the system could cause denial of service, potentially disrupting critical services or operations. This could affect availability of systems used in industrial control, research, or legacy infrastructure that has not been upgraded. However, given the age and rarity of Cyrix CPUs in modern deployments, the overall risk to European enterprises is low. Organizations relying on legacy hardware in sectors such as manufacturing, education, or government archives may face operational interruptions if this vulnerability is exploited. The lack of remote exploitability and requirement for local access further reduces the threat surface. Nonetheless, any disruption to availability in critical systems can have cascading effects on business continuity and service delivery.

Mitigation Recommendations

Since no patch is available due to the hardware nature of the vulnerability, mitigation focuses on limiting exposure and access. European organizations should: 1) Identify and inventory any legacy systems running Linux on Cyrix CPUs and assess their criticality. 2) Restrict local access to these systems by enforcing strict physical and logical access controls, including multi-factor authentication and role-based access. 3) Where possible, replace or upgrade legacy hardware to modern CPUs not affected by this issue. 4) Implement monitoring to detect unusual system crashes or hangs indicative of exploitation attempts. 5) Use virtualization or containerization to isolate legacy environments, minimizing the impact of potential DoS conditions. 6) Educate system administrators about the vulnerability and the importance of limiting local user privileges on affected systems. These steps help reduce the risk of local DoS attacks exploiting this hardware bug.

Need more detailed analysis?Upgrade to Pro Console

Threat ID: 682ca32bb6fd31d6ed7dede5

Added to database: 5/20/2025, 3:43:39 PM

Last enriched: 7/1/2025, 7:56:30 PM

Last updated: 2/7/2026, 7:08:10 AM

Views: 38

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats