CVE-2024-47686: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate() The psc->div[] array has psc->num_div elements. These values come from when we call clk_hw_register_div(). It's adc_divisors and ARRAY_SIZE(adc_divisors)) and so on. So this condition needs to be >= instead of > to prevent an out of bounds read.
AI Analysis
Technical Summary
CVE-2024-47686 is a vulnerability identified in the Linux kernel specifically related to the ep93xx clock driver. The issue arises from an off-by-one error in the function ep93xx_div_recalc_rate(). The vulnerability is due to improper boundary checking on the psc->div[] array, which holds divisor values used for clock rate calculations. The array has psc->num_div elements, and these values are derived from calls to clk_hw_register_div() with parameters such as adc_divisors and ARRAY_SIZE(adc_divisors). The original code uses a condition that checks if an index is greater than the number of elements (psc->num_div), but this should be a greater than or equal to (>=) check to prevent an out-of-bounds read. This off-by-one error can lead to reading memory beyond the allocated array bounds, potentially causing undefined behavior such as kernel crashes or information disclosure. The vulnerability does not appear to have any known exploits in the wild at the time of publication, and no CVSS score has been assigned yet. The fix involves correcting the boundary check condition to prevent out-of-bounds access. This vulnerability affects specific versions of the Linux kernel identified by commit hashes, indicating it is a code-level flaw in the kernel's clock subsystem for the ep93xx platform, which is a less common embedded ARM architecture. While the vulnerability is technical and low-level, improper memory access in kernel space can have serious consequences, including system instability or privilege escalation if exploited in conjunction with other vulnerabilities.
Potential Impact
For European organizations, the impact of CVE-2024-47686 depends largely on the deployment of Linux systems running the affected kernel versions on ep93xx hardware platforms. Since ep93xx is an embedded ARM architecture primarily used in specialized industrial or embedded devices, the vulnerability's direct impact on mainstream enterprise Linux servers or desktops is limited. However, organizations in sectors such as manufacturing, industrial control systems, telecommunications, or IoT deployments that utilize ep93xx-based devices running Linux could face risks. Exploitation could lead to kernel crashes causing denial of service or, in worst cases, information leakage or escalation of privileges if combined with other vulnerabilities. This could disrupt critical infrastructure or industrial processes. Additionally, since the Linux kernel is widely used across Europe, any embedded systems or niche devices using this platform could be indirectly affected. The absence of known exploits reduces immediate risk, but the vulnerability should be addressed promptly to prevent future exploitation. The impact on confidentiality, integrity, and availability is primarily availability (due to potential crashes) and possibly integrity if memory corruption occurs.
Mitigation Recommendations
European organizations should take the following specific mitigation steps: 1) Identify and inventory all Linux systems running on ep93xx hardware or using affected kernel versions, especially in embedded or industrial environments. 2) Apply the official Linux kernel patches that fix the off-by-one boundary check in ep93xx_div_recalc_rate() as soon as they become available. Monitor Linux kernel mailing lists and vendor advisories for patch releases. 3) For devices where patching the kernel is not immediately feasible, consider isolating or segmenting affected devices within the network to limit potential exploitation impact. 4) Implement strict access controls and monitoring on embedded devices to detect abnormal behavior or crashes that could indicate exploitation attempts. 5) Engage with hardware and software vendors to confirm whether their products are affected and request timely firmware or kernel updates. 6) Incorporate this vulnerability into vulnerability management and incident response plans, ensuring readiness to respond to any emerging exploits. 7) For critical industrial systems, perform risk assessments to evaluate the necessity of temporary compensating controls until patches are applied.
Affected Countries
Germany, France, United Kingdom, Italy, Netherlands, Sweden, Finland, Poland
CVE-2024-47686: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate() The psc->div[] array has psc->num_div elements. These values come from when we call clk_hw_register_div(). It's adc_divisors and ARRAY_SIZE(adc_divisors)) and so on. So this condition needs to be >= instead of > to prevent an out of bounds read.
AI-Powered Analysis
Technical Analysis
CVE-2024-47686 is a vulnerability identified in the Linux kernel specifically related to the ep93xx clock driver. The issue arises from an off-by-one error in the function ep93xx_div_recalc_rate(). The vulnerability is due to improper boundary checking on the psc->div[] array, which holds divisor values used for clock rate calculations. The array has psc->num_div elements, and these values are derived from calls to clk_hw_register_div() with parameters such as adc_divisors and ARRAY_SIZE(adc_divisors). The original code uses a condition that checks if an index is greater than the number of elements (psc->num_div), but this should be a greater than or equal to (>=) check to prevent an out-of-bounds read. This off-by-one error can lead to reading memory beyond the allocated array bounds, potentially causing undefined behavior such as kernel crashes or information disclosure. The vulnerability does not appear to have any known exploits in the wild at the time of publication, and no CVSS score has been assigned yet. The fix involves correcting the boundary check condition to prevent out-of-bounds access. This vulnerability affects specific versions of the Linux kernel identified by commit hashes, indicating it is a code-level flaw in the kernel's clock subsystem for the ep93xx platform, which is a less common embedded ARM architecture. While the vulnerability is technical and low-level, improper memory access in kernel space can have serious consequences, including system instability or privilege escalation if exploited in conjunction with other vulnerabilities.
Potential Impact
For European organizations, the impact of CVE-2024-47686 depends largely on the deployment of Linux systems running the affected kernel versions on ep93xx hardware platforms. Since ep93xx is an embedded ARM architecture primarily used in specialized industrial or embedded devices, the vulnerability's direct impact on mainstream enterprise Linux servers or desktops is limited. However, organizations in sectors such as manufacturing, industrial control systems, telecommunications, or IoT deployments that utilize ep93xx-based devices running Linux could face risks. Exploitation could lead to kernel crashes causing denial of service or, in worst cases, information leakage or escalation of privileges if combined with other vulnerabilities. This could disrupt critical infrastructure or industrial processes. Additionally, since the Linux kernel is widely used across Europe, any embedded systems or niche devices using this platform could be indirectly affected. The absence of known exploits reduces immediate risk, but the vulnerability should be addressed promptly to prevent future exploitation. The impact on confidentiality, integrity, and availability is primarily availability (due to potential crashes) and possibly integrity if memory corruption occurs.
Mitigation Recommendations
European organizations should take the following specific mitigation steps: 1) Identify and inventory all Linux systems running on ep93xx hardware or using affected kernel versions, especially in embedded or industrial environments. 2) Apply the official Linux kernel patches that fix the off-by-one boundary check in ep93xx_div_recalc_rate() as soon as they become available. Monitor Linux kernel mailing lists and vendor advisories for patch releases. 3) For devices where patching the kernel is not immediately feasible, consider isolating or segmenting affected devices within the network to limit potential exploitation impact. 4) Implement strict access controls and monitoring on embedded devices to detect abnormal behavior or crashes that could indicate exploitation attempts. 5) Engage with hardware and software vendors to confirm whether their products are affected and request timely firmware or kernel updates. 6) Incorporate this vulnerability into vulnerability management and incident response plans, ensuring readiness to respond to any emerging exploits. 7) For critical industrial systems, perform risk assessments to evaluate the necessity of temporary compensating controls until patches are applied.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-09-30T16:00:12.941Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9825c4522896dcbe0501
Added to database: 5/21/2025, 9:08:53 AM
Last enriched: 6/28/2025, 7:39:32 PM
Last updated: 7/27/2025, 3:02:54 PM
Views: 8
Related Threats
CVE-2025-8834: Cross Site Scripting in JCG Link-net LW-N915R
MediumCVE-2025-55159: CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer in tokio-rs slab
MediumCVE-2025-55161: CWE-918: Server-Side Request Forgery (SSRF) in Stirling-Tools Stirling-PDF
HighCVE-2025-25235: CWE-918 Server-Side Request Forgery (SSRF) in Omnissa Secure Email Gateway
HighCVE-2025-55151: CWE-918: Server-Side Request Forgery (SSRF) in Stirling-Tools Stirling-PDF
HighActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.