rose: Fix NULL pointer dereference in rose_send_frame()
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: 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 [...] 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
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.14.299, 4.19.265, 4.9.333, 5.10.154, 5.15.78, 5.4.224, 6.0.8
- CVEs
- CVE-2022-49916
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 16:36 UTC · Revision 1
Source evidence
rose: Fix NULL pointer dereference in rose_send_frame()
core-osv · Original sourcePublished 1 May 2025, 14:10 UTC
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: 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 [...] 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
osv:CVE-2022-49916
Kernel
Fixed versions: 4.9.333, 4.14.299, 4.19.265, 5.4.224, 5.10.154, 5.15.78, 6.0.8
Complete source record
{
"id": "2ff4e9dce410d86397f253051d989792e074f83e5fc7d69496c4ae864769b9ea",
"url": "https://osv.dev/vulnerability/CVE-2022-49916",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "rose: Fix NULL pointer dereference in rose_send_frame()",
"summary": "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: 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 [...] 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 ",
"evidence": "osv:CVE-2022-49916",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.9.333",
"evidence": "/affected/1/ranges"
},
{
"value": "4.14.299",
"evidence": "/affected/1/ranges"
},
{
"value": "4.19.265",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.224",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.154",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.78",
"evidence": "/affected/1/ranges"
},
{
"value": "6.0.8",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "CVE-2022-49916",
"aliases": [
"CVE-2022-49916"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "76885373129b13df35ecc9b4ee86ea5840f12133"
},
{
"fixed": "01b9c68c121847d05a4ccef68244dadf82bfa331"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "b8f9de195d6303f52bae16c7911f35ac14ba7e3d"
},
{
"fixed": "bbc03d74e641e824754443b908454ca9e203773e"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "0aae33feb7a56b28318f92c960a3d08d9c305984"
},
{
"fixed": "5b46adfbee1e429f33b10a88d6c00fa88f3d6c77"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "6e4b20d548fc97ecbdca15c8d96302ee5e3e6313"
},
{
"fixed": "b13be5e852b03f376058027e462fad4230240891"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "de3deadd11987070788b48825bec4647458b988d"
},
{
"fixed": "f06186e5271b980bac03f5c97276ed0146ddc9b0"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "9cf85759e104d7e9c3fd8920a554195b715d6797"
},
{
"fixed": "3e2129c67daca21043a26575108f6286c85e71f6"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "3c53cd65dece47dd1f9d3a809f32e59d1d87b2b8"
},
{
"fixed": "a601e5eded33bb88b8a42743db8fef3ad41dd97e"
},
{
"fixed": "e97c089d7a49f67027395ddf70bf327eeac2611e"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "4.9.327"
},
{
"fixed": "4.9.333"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "4.14.292"
},
{
"fixed": "4.14.299"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "4.19.257"
},
{
"fixed": "4.19.265"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "5.4.212"
},
{
"fixed": "5.4.224"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "5.10.140"
},
{
"fixed": "5.10.154"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "5.15.64"
},
{
"fixed": "5.15.78"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "5.19.6"
},
{
"fixed": "5.20"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "9197ca40fd9de265caedba70d0cb5814c4e45952"
}
]
}
],
"versions": [
"v4.9.332",
"v4.9.331",
"v4.9.330",
"v4.9.329",
"v4.9.328",
"v4.9.327",
"v4.14.298",
"v4.14.297",
"v4.14.296",
"v4.14.295",
"v4.14.294",
"v4.14.293",
"v4.14.292",
"v4.19.264",
"v4.19.263",
"v4.19.262",
"v4.19.261",
"v4.19.260",
"v4.19.259",
"v4.19.258",
"v4.19.257",
"v5.4.223",
"v5.4.222",
"v5.4.221",
"v5.4.220",
"v5.4.219",
"v5.4.218",
"v5.4.217",
"v5.4.216",
"v5.4.215",
"v5.4.214",
"v5.4.213",
"v5.4.212",
"v5.10.153",
"v5.10.152",
"v5.10.151",
"v5.10.150",
"v5.10.149",
"v5.10.148",
"v5.10.147",
"v5.10.146",
"v5.10.145",
"v5.10.144",
"v5.10.143",
"v5.10.142",
"v5.10.141",
"v5.10.140",
"v5.15.77",
"v5.15.76",
"v5.15.75",
"v5.15.74",
"v5.15.73",
"v5.15.72",
"v5.15.71",
"v5.15.70",
"v5.15.69",
"v5.15.68",
"v5.15.67",
"v5.15.66",
"v5.15.65",
"v5.15.64",
"v5.19.17",
"v5.19.16",
"v5.19.15",
"v5.19.14",
"v5.19.13",
"v5.19.12",
"v5.19.11",
"v5.19.10",
"v5.19.9",
"v5.19.8",
"v5.19.7",
"v5.19.6"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49916.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "4.9.333"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.10.0"
},
{
"fixed": "4.14.299"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.15.0"
},
{
"fixed": "4.19.265"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.224"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.154"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.78"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.0.8"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49916.json"
}
}
],
"modified": "2026-10-28T02:30:30.755779687Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/01b9c68c121847d05a4ccef68244dadf82bfa331",
"https://git.kernel.org/stable/c/3e2129c67daca21043a26575108f6286c85e71f6",
"https://git.kernel.org/stable/c/5b46adfbee1e429f33b10a88d6c00fa88f3d6c77",
"https://git.kernel.org/stable/c/a601e5eded33bb88b8a42743db8fef3ad41dd97e",
"https://git.kernel.org/stable/c/b13be5e852b03f376058027e462fad4230240891",
"https://git.kernel.org/stable/c/bbc03d74e641e824754443b908454ca9e203773e",
"https://git.kernel.org/stable/c/e97c089d7a49f67027395ddf70bf327eeac2611e",
"https://git.kernel.org/stable/c/f06186e5271b980bac03f5c97276ed0146ddc9b0",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49916.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-49916",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49916.json"
}
},
"related_cves": [
{
"value": "CVE-2022-49916",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 497458,
"published_at": "2025-05-01T14:10:56.851+00:00"
}