Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-43015

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: net: macb: fix clk handling on PCI glue driver removal platform_device_unregister() may still want to use the registered clks d…

Published May 1, 2026CWE-416EPSS 0.17%

Overview

CVE-2026-43015 is a high-severity vulnerability. It was published on May 1, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. 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:

net: macb: fix clk handling on PCI glue driver removal

platform_device_unregister() may still want to use the registered clks

during runtime resume callback.

Note that there is a commit d82d5303c4c5 ("net: macb: fix use after free

on rmmod") that addressed the similar problem of clk vs platform device

unregistration but just moved the bug to another place.

Save the pointers to clks into local variables for reuse after platform

device is unregistered.

BUG: KASAN: use-after-free in clk_prepare+0x5a/0x60

Read of size 8 at addr ffff888104f85e00 by task modprobe/597

CPU: 2 PID: 597 Comm: modprobe Not tainted 6.1.164+ #114

Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.1-0-g3208b098f51a-prebuilt.qemu.org 04/01/2014

Call Trace:

<TASK>

dump_stack_lvl+0x8d/0xba

print_report+0x17f/0x496

kasan_report+0xd9/0x180

clk_prepare+0x5a/0x60

macb_runtime_resume+0x13d/0x410 [macb]

pm_generic_runtime_resume+0

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. 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.

References

Refgit.kernel.org/stable/c/16ab4c0e2b15df5d33bfcb9ea8e4441b85dd4a57Refgit.kernel.org/stable/c/2d96204e4184d6f7dd2f93c6f218fd0c1f55e9aeRefgit.kernel.org/stable/c/3496fb9e66f79d4def3bb7ec7563e3eaa33a688fRefgit.kernel.org/stable/c/67f70841a175fa3469119f52d77a3662c07507a2Refgit.kernel.org/stable/c/b3f799cdf830df1782ae463cf15ace35015be99eRefgit.kernel.org/stable/c/bf64cae913cdd4821f13d5d1d68900c0891bef69Refgit.kernel.org/stable/c/ce8fe5287b87e24e225c342f3b0ec04f0b3680feRefgit.kernel.org/stable/c/f310a836da90d0f0321b14d446c071af63f9ee4c

How CyberStrike helps

Frequently asked questions

What is CVE-2026-43015?

CVE-2026-43015 is a high-severity vulnerability. It was published on May 1, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-43015?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-43015?

Check the references section for vendor advisories, patches, and mitigation guidance. 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-2026-43015?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-43015 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999