Bug 2502280 (CVE-2026-63857) - CVE-2026-63857 kernel: net: airoha: Do not read uninitialized fragment address in airoha_dev_xmit()
Summary: CVE-2026-63857 kernel: net: airoha: Do not read uninitialized fragment addres...
Keywords:
Status: NEW
Alias: CVE-2026-63857
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-19 15:01 UTC by OSIDB Bzimport
Modified: 2026-07-23 09:09 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-07-19 15:01:45 UTC
In the Linux kernel, the following vulnerability has been resolved:

net: airoha: Do not read uninitialized fragment address in airoha_dev_xmit()

The transmit loop in airoha_dev_xmit() reads fragment address and length
during its final iteration, when the loop index equals
skb_shinfo(skb)->nr_frags, at which point the fragment data is
uninitialized. While these values are never consumed, the read itself is
unsafe and may trigger a page fault. Fix this by avoiding the fragment
read on the last iteration.
Additionally, move the skb pointer from the first to the last used packet
descriptor, so that airoha_qdma_tx_napi_poll() defers freeing the skb
until the final descriptor is processed.

Comment 2 JesseWolfe 2026-07-23 09:09:17 UTC
I really appreciate the in-depth analysis of CVE-2026-63857! It’s crucial for us to tackle these uninitialized fragment address issues, especially given how they can impact overall system stability. I had a similar experience when diagnosing TCP issues in our network; it taught me the importance of thorough initialization. Thanks for shedding light on such an important topic! https://spacewavesgame.io


Note You need to log in before you can comment on or make changes to this bug.