CVE-2024-43824

What it actually does

Removes redundant NULL check on cached epc_features in pci_epf_test_core_init() after prior validation in bind(), eliminating a false-positive Smatch warning and preventing potential NULL pointer dereference that could lead to memory corruption in the Linux kernel PCI endpoint test function.

Why it matters to the business

May cause kernel instability or crashes on systems using PCI endpoint functionality, impacting 226 downstream dependents with low but non-zero exploit probability and no known active campaigns.

How an attack unfolds

An attacker triggers PCI endpoint function binding and core initialization paths to reach the dereference site before caching completes, resulting in a NULL access that can be used for denial of service or limited memory corruption; no named threat actors or ransomware usage reported.

How to fix it

Apply the upstream kernel commit that caches epc_features and removes the redundant check; no httpx packages are involved despite erroneous listing.

How to confirm the fix worked

Confirm the patch is present by inspecting drivers/pci/endpoint/functions/pci-epf-test.c for direct use of cached epc_features without the NULL check at line 784 and verify absence of the prior Smatch warning.

Typical attack path

1. Obtain local or privileged access to a system with PCI endpoint support enabled
2. Load or trigger the pci-epf-test function binding
3. Force execution of pci_epf_test_core_init() to hit the uncached epc_features dereference
4. Leverage resulting NULL pointer dereference for crash or corruption

How to detect it

Search kernel logs and dmesg for NULL pointer dereference faults originating from pci_epf_test_core_init(); review Smatch or static analysis reports mentioning epc_features at pci-epf-test.c:784 and 747.

• pci_epf_test_core_init
• epc_features
• drivers/pci/endpoint/functions/pci-epf-test.c:784

What your security team should do

• Prioritize kernel updates containing commit a01e7214bef9 and the referenced fix for all affected distributions
• Monitor EPSS trend (stable at ~0.002) and re-evaluate if new exploit code appears
• Audit PCI endpoint configurations in test or embedded environments for exposure