CVE-2024-26707: net: hsr: remove WARN_ONCE() in send_hsr_supervision_frame()
In the Linux kernel, the following vulnerability has been resolved:
net: hsr: remove WARN_ONCE() in send_hsr_supervision_frame()
Syzkaller reported [1] hitting a warning after failing to allocate
resources for skb in hsr_init_skb(). Since a WARN_ONCE() call will
not help much in this case, it might be prudent to switch to
netdev_warn_once(). At the very least it will suppress syzkaller
reports such as [1].
Just in case, use netdev_warn_once() in send_prp_supervision_frame()
for similar reasons.
[1]
HSR: Could not send supervision frame
WARNING: CPU: 1 PID: 85 at net/hsr/hsr_device.c:294 send_hsr_supervision_frame+0x60a/0x810 net/hsr/hsr_device.c:294
RIP: 0010:send_hsr_supervision_frame+0x60a/0x810 net/hsr/hsr_device.c:294
...
Call Trace:
<IRQ>
hsr_announce+0x114/0x370 net/hsr/hsr_device.c:382
call_timer_fn+0x193/0x590 kernel/time/timer.c:1700
expire_timers kernel/time/timer.c:1751 [inline]
__run_timers+0x764/0xb20 kernel/time/timer.c:2022
run_timer_softirq+0x58/0xd0 kernel/time/timer.c:2035
__do_softirq+0x21a/0x8de kernel/softirq.c:553
invoke_softirq kernel/softirq.c:427 [inline]
__irq_exit_rcu kernel/softirq.c:632 [inline]
irq_exit_rcu+0xb7/0x120 kernel/softirq.c:644
sysvec_apic_timer_interrupt+0x95/0xb0 arch/x86/kernel/apic/apic.c:1076
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:649
...
This issue is also found in older kernels (at least up to 5.10).
Security readout for executives and security teams
Plain-English summary
CVE-2024-26707 is a Linux kernel issue in HSR/PRP networking error handling. A failed packet allocation could trigger a kernel warning report. The upstream fix changes the warning path, reducing disruptive warning behavior rather than describing data theft or direct remote compromise.
Executive priority
Handle through normal kernel patch management unless HSR/PRP is operationally important in your environment. There is no source-backed evidence of active exploitation or severe business impact in the provided bundle.
Technical view
The flaw is in net/hsr/hsr_device.c around send_hsr_supervision_frame(), with a similar PRP path adjusted. When hsr_init_skb() fails to allocate resources, WARN_ONCE() could fire from timer/IRQ context. Stable kernel commits replace it with netdev_warn_once().
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with HSR/PRP networking code present or used. The source lists Linux 5.9 through several stable branches and notes older kernels, at least up to 5.10, also contain the issue.
Exploitation context
The bundle cites Syzkaller finding the warning. It does not cite active exploitation, KEV listing, public exploitation, privilege escalation, or remote code execution. Treat exploitation evidence as incomplete and currently unsupported by the provided sources.
Researcher notes
The CVE appears rooted in warning behavior after allocation failure, not a clearly described memory corruption primitive. The source does not provide CVSS, CWE, exploitability analysis, or a complete affected-version matrix beyond Linux kernel branches and stable commits.
Mitigation direction
Apply vendor kernel updates containing the referenced stable kernel fixes.
For Debian systems, review the cited Debian LTS advisory and update accordingly.
If vendor status is unclear, check kernel vendor guidance for CVE-2024-26707.
Avoid enabling or relying on HSR/PRP networking unless operationally required.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and embedded systems.
Check whether deployed kernels include the referenced stable commits or downstream vendor fixes.
Identify systems using HSR/PRP networking functionality.
Review kernel logs for HSR supervision-frame warning messages.
Confirm vendor advisories map your distribution kernel package to this CVE.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-26707 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.