ax25: properly unshare skbs in ax25_kiss_rcv()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 89064cf534bea4bb28c83fe6bbb26657b19dd5fe| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ax25: properly unshare skbs in ax25_kiss_rcv()
Bernard Pidoux reported a regression apparently caused by commit c353e8983e0d ("net: introduce per netns packet chains").
skb->dev becomes NULL and we crash in __netif_receive_skb_core().
Before above commit, different kind of bugs or corruptions could happen without a major crash.
But the root cause is that ax25_kiss_rcv() can queue/mangle input skb without checking if this skb is shared or not.
Many thanks to Bernard Pidoux for his help, diagnosis and tests.
We had a similar issue years ago fixed with commit 7aaed57c5c28 ("phonet: properly unshare skbs in phonet_rcv()").
From the CVE record · Linux
The Linux kernel’s ax25_kiss_rcv() can queue or modify a shared incoming packet buffer without first unsharing it. When such a packet is received, skb->dev can become NULL and the kernel can crash. The input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with AX.25 receive handling should check their kernel versions against the vendor advisory; affected versions are not specified here.