nfc: nci: add data_len bound checks to activation parameter extractors
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e8c0dacd9836dc2dcb28d236c9cc3cfaa9965a20 · < 9620a91f8d643b680f417a435db399a04d1e06d8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nfc: nci: add data_len bound checks to activation parameter extractors
nci_extract_activation_params_iso_dep() and nci_extract_activation_params_nfc_dep() read an inner length byte from the NCI RF_INTF_ACTIVATED_NTF payload and use it to memcpy() into fixed kernel buffers, but neither function receives the caller-validated activation_params_len. A crafted NCI notification with activation_params_len=1 and an inner length byte of up to 20 (NFC-A) or 50 (NFC-B) causes memcpy() to read that many bytes past the one valid byte in the activation params region -- a slab out-of-bounds read of kernel memory adjacent to the NCI skb.
The sibling nci_extract_rf_params_*() family was given equivalent protection by commit 571dcbeb8e63 ("net: nfc: nci: Fix parameter validation for packet data"), but the two activation parameter extractors were not updated at that time.
Add a data_len parameter to both functions, guard against an empty region before consuming the inner length byte, decrement the remaining count after consuming it, and clamp the copy length to what is actually available. Update both call sites to pass ntf.activation_params_len, which is already validated against the skb at ntf.c:801.
From the CVE record · Linux
The Linux kernel’s NFC NCI activation parameter extractors can read past the end of a notification’s validated activation parameters. A crafted NCI RF_INTF_ACTIVATED_NTF notification with a short activation parameters region and a larger inner length byte can trigger a slab out-of-bounds read of adjacent kernel memory.
Engineers running Linux kernels with the affected NFC NCI code should check their kernel versions against the vendor advisory; affected versions are not specified in the input.