CVE-2022-49916

rose: Fix NULL pointer dereference in rose_send_frame()

MEDIUM
5.5
CVSS Score
Published: May 1, 2025 at 02:10 PM UTC
Updated: June 17, 2026 at 05:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: rose: Fix NULL pointer dereference in rose_send_frame() The syzkaller reported an issue: KASAN: null-ptr-deref in range [0x0000000000000380-0x0000000000000387] CPU: 0 PID: 4069 Comm: kworker/0:15 Not tainted 6.0.0-syzkaller-02734-g0326074ff465 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Workqueue: rcu_gp srcu_invoke_callbacks RIP: 0010:rose_send_frame+0x1dd/0x2f0 net/rose/rose_link.c:101 Call Trace: <IRQ> rose_transmit_clear_request+0x1d5/0x290 net/rose/rose_link.c:255 rose_rx_call_request+0x4c0/0x1bc0 net/rose/af_rose.c:1009 rose_loopback_timer+0x19e/0x590 net/rose/rose_loopback.c:111 call_timer_fn+0x1a0/0x6b0 kernel/time/timer.c:1474 expire_timers kernel/time/timer.c:1519 [inline] __run_timers.part.0+0x674/0xa80 kernel/time/timer.c:1790 __run_timers kernel/time/timer.c:1768 [inline] run_timer_softirq+0xb3/0x1d0 kernel/time/timer.c:1803 __do_softirq+0x1d0/0x9c8 kernel/softirq.c:571 [...] </IRQ> It triggers NULL pointer dereference when 'neigh->dev->dev_addr' is called in the rose_send_frame(). It's the first occurrence of the `neigh` is in rose_loopback_timer() as `rose_loopback_neigh', and the 'dev' in 'rose_loopback_neigh' is initialized sa nullptr. It had been fixed by commit 3b3fd068c56e3fbea30090859216a368398e39bf ("rose: Fix Null pointer dereference in rose_send_frame()") ever. But it's introduced by commit 3c53cd65dece47dd1f9d3a809f32e59d1d87b2b8 ("rose: check NULL rose_loopback_neigh->loopback") again. We fix it by add NULL check in rose_transmit_clear_request(). When the 'dev' in 'neigh' is NULL, we don't reply the request and just clear it. syzkaller don't provide repro, and I provide a syz repro like: r0 = syz_init_net_socket$bt_sco(0x1f, 0x5, 0x2) ioctl$sock_inet_SIOCSIFFLAGS(r0, 0x8914, &(0x7f0000000180)={'rose0\x00', 0x201}) r1 = syz_init_net_socket$rose(0xb, 0x5, 0x0) bind$rose(r1, &(0x7f00000000c0)=@full={0xb, @dev, @null, 0x0, [@null, @null, @netrom, @netrom, @default, @null]}, 0x40) connect$rose(r1, &(0x7f0000000240)=@short={0xb, @dev={0xbb, 0xbb, 0xbb, 0x1, 0x0}, @remote={0xcc, 0xcc, 0xcc, 0xcc, 0xcc, 0xcc, 0x1}, 0x1, @netrom={0xbb, 0xbb, 0xbb, 0xbb, 0xbb, 0x0, 0x0}}, 0x1c)

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.19.64.14.292 ≤ v < 4.14.2994.19.257 ≤ v < 4.19.2654.9.327 ≤ v < 4.9.3335.10.140 ≤ v < 5.10.1545.15.64 ≤ v < 5.15.785.19.6 ≤ v < 5.205.19.6 ≤ v < 6.0.85.4.212 ≤ v < 5.4.2246.0 ≤ v < 6.0.86.0 ≤ v < 6.10aae33feb7a56b28318f92c960a3d08d9c3059843c53cd65dece47dd1f9d3a809f32e59d1d87b2b84.14.2924.19.2574.9.3275.10.1405.15.645.19.65.4.2126.1 rc16.1 rc26.1 rc36e4b20d548fc97ecbdca15c8d96302ee5e3e631376885373129b13df35ecc9b4ee86ea5840f121339197ca40fd9de265caedba70d0cb5814c4e459529cf85759e104d7e9c3fd8920a554195b715d6797b8f9de195d6303f52bae16c7911f35ac14ba7e3dde3deadd11987070788b48825bec4647458b988d
Vendor states this is fixed in 01b9c68c121847d05a4ccef68244dadf82bfa331 (fixed)
Vendor states this is fixed in 3e2129c67daca21043a26575108f6286c85e71f6 (fixed)
Vendor states this is fixed in 5b46adfbee1e429f33b10a88d6c00fa88f3d6c77 (fixed)
Vendor states this is fixed in a601e5eded33bb88b8a42743db8fef3ad41dd97e (fixed)
Vendor states this is fixed in b13be5e852b03f376058027e462fad4230240891 (fixed)
Vendor states this is fixed in bbc03d74e641e824754443b908454ca9e203773e (fixed)
Vendor states this is fixed in e97c089d7a49f67027395ddf70bf327eeac2611e (fixed)
Vendor states this is fixed in f06186e5271b980bac03f5c97276ed0146ddc9b0 (fixed)
Vendor states this is fixed in 4.14.299 (unaffected)
Vendor states this is fixed in 4.19.265 (unaffected)
Vendor states this is fixed in 4.9.333 (unaffected)
Vendor states this is fixed in 5.10.154 (unaffected)
Vendor states this is fixed in 5.15.78 (unaffected)
Affected range stops below 5.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.4.224 (unaffected)
Vendor states this is fixed in 6.0 (unaffected)
Vendor states this is fixed in 6.0.8 (unaffected)
Vendor states this is fixed in 6.1 (unaffected)

References (8)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/01b9c68c121847d05a4ccef68244dadf82bfa331
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/3e2129c67daca21043a26575108f6286c85e71f6
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/5b46adfbee1e429f33b10a88d6c00fa88f3d6c77
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/a601e5eded33bb88b8a42743db8fef3ad41dd97e
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b13be5e852b03f376058027e462fad4230240891
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/bbc03d74e641e824754443b908454ca9e203773e
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/e97c089d7a49f67027395ddf70bf327eeac2611e
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/f06186e5271b980bac03f5c97276ed0146ddc9b0

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card