CVE-2024-56697
5.5 · MEDIUMOverview
CVE-2024-56697 is a medium-severity vulnerability affecting linux linux_kernel. It was published on December 28, 2024 and has a CVSS 3.1 base score of 5.5 (MEDIUM).
This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.
Technical Description
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: Fix the memory allocation issue in amdgpu_discovery_get_nps_info()
Fix two issues with memory allocation in amdgpu_discovery_get_nps_info()
for mem_ranges:
- Add a check for allocation failure to avoid dereferencing a null
pointer.
- As suggested by Christophe, use kvcalloc() for memory allocation,
which checks for multiplication overflow.
Additionally, assign the output parameters nps_type and range_cnt after
the kvcalloc() call to prevent modifying the output parameters in case
of an error return.
Remediation
Check the references section for vendor advisories and patches from linux. Update linux_kernel to the latest patched version. 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.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| linux | linux_kernel | >= 6.11, < 6.11.11 | Affected |
Frequently Asked Questions
What is CVE-2024-56697?
CVE-2024-56697 is a medium-severity vulnerability affecting linux linux_kernel. It was published on December 28, 2024 and has a CVSS 3.1 base score of 5.5 (MEDIUM).
How severe is CVE-2024-56697?
This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.
How do I fix or remediate CVE-2024-56697?
Check the references section for vendor advisories and patches from linux. Update linux_kernel to the latest patched version. 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-2024-56697?
CyberStrike's AI-powered security agents can automatically detect CVE-2024-56697 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related MEDIUM CVEs from 2024
View all →OCSInventory allow stored email template with special characters that lead to a Stored cross-site Sc
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation