CVE-2024-42130
Android Linux NFC NAL Underflow
Description
In the Linux kernel, the following vulnerability has been resolved: nfc/nci: Add the inconsistency check between the input data length and count write$nci(r0, &(0x7f0000000740)=ANY=[@ANYBLOB="610501"], 0xf) Syzbot constructed a write() call with a data length of 3 bytes but a count value of 15, which passed too little data to meet the basic requirements of the function nci_rf_intf_activated_ntf_packet(). Therefore, increasing the comparison between data length and count value to avoid problems caused by inconsistent data length and count.
INFO
Published Date :
July 30, 2024, 8:15 a.m.
Last Modified :
Nov. 21, 2024, 9:33 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-42130.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-42130 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-42130
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-42130 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-42130 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/056478b4321b36ca33567089d39ac992f6c9c37a Added Reference https://git.kernel.org/stable/c/068648aab72c9ba7b0597354ef4d81ffaac7b979 Added Reference https://git.kernel.org/stable/c/22a72c1c10f43ca645a98725e0faff34592f4d08 Added Reference https://git.kernel.org/stable/c/41f5e2840cd0629f049ce5ce2f8dd10a8299de42 Added Reference https://git.kernel.org/stable/c/f07bcd8bba803c9e6ad2048543185d6c56587a2f -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 30, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: nfc/nci: Add the inconsistency check between the input data length and count write$nci(r0, &(0x7f0000000740)=ANY=[@ANYBLOB="610501"], 0xf) Syzbot constructed a write() call with a data length of 3 bytes but a count value of 15, which passed too little data to meet the basic requirements of the function nci_rf_intf_activated_ntf_packet(). Therefore, increasing the comparison between data length and count value to avoid problems caused by inconsistent data length and count. Added Reference kernel.org https://git.kernel.org/stable/c/f07bcd8bba803c9e6ad2048543185d6c56587a2f [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/41f5e2840cd0629f049ce5ce2f8dd10a8299de42 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/056478b4321b36ca33567089d39ac992f6c9c37a [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/22a72c1c10f43ca645a98725e0faff34592f4d08 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/068648aab72c9ba7b0597354ef4d81ffaac7b979 [No types assigned]