CVE-2022-49916: rose: Fix NULL pointer dereference in rose_send_frame()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 01b9c68c121847d05a4ccef68244dadf82bfa331, 3e2129c67daca21043a26575108f6286c85e71f6, 4.14.299.
Low priority for now. Upgrade to Linux Linux 01b9c68c121847d05a4ccef68244dadf82bfa331, 3e2129c67daca21043a26575108f6286c85e71f6, 4.14.299 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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)
- Published
- May 1, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.9.327 and later · before 4.9.333
- linux linux kernel4.14.292 and later · before 4.14.299
- linux linux kernel4.19.257 and later · before 4.19.265
- linux linux kernel5.4.212 and later · before 5.4.224
- linux linux kernel5.10.140 and later · before 5.10.154
- linux linux kernel5.15.64 and later · before 5.15.78
- linux linux kernel5.19.6 and later · before 6.0.8
- linux linux kernel6.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 9197ca40fd9de265caedba70d0cb5814c4e45952, 6.0affected
- 76885373129b13df35ecc9b4ee86ea5840f12133 and later · before 01b9c68c121847d05a4ccef68244dadf82bfa331affected · git
- b8f9de195d6303f52bae16c7911f35ac14ba7e3d and later · before bbc03d74e641e824754443b908454ca9e203773eaffected · git
- 0aae33feb7a56b28318f92c960a3d08d9c305984 and later · before 5b46adfbee1e429f33b10a88d6c00fa88f3d6c77affected · git
- 6e4b20d548fc97ecbdca15c8d96302ee5e3e6313 and later · before b13be5e852b03f376058027e462fad4230240891affected · git
- de3deadd11987070788b48825bec4647458b988d and later · before f06186e5271b980bac03f5c97276ed0146ddc9b0affected · git
- 9cf85759e104d7e9c3fd8920a554195b715d6797 and later · before 3e2129c67daca21043a26575108f6286c85e71f6affected · git
- 3c53cd65dece47dd1f9d3a809f32e59d1d87b2b8 and later · before a601e5eded33bb88b8a42743db8fef3ad41dd97eaffected · git
- 3c53cd65dece47dd1f9d3a809f32e59d1d87b2b8 and later · before e97c089d7a49f67027395ddf70bf327eeac2611eaffected · git
- 4.9.327 and later · before 4.9.333affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.0.8-1 | 6.0.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49914May 1, 2025 · btrfs: fix inode list leak during backref walking at resolve_indirect_refs()22Monitor
- ← EarlierCVE-2022-49915May 1, 2025 · mISDN: fix possible memory leak in mISDN_register_device()22Monitor
- Later →CVE-2022-49917May 1, 2025 · ipvs: fix WARNING in ip_vs_app_net_cleanup()31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 01b9c68c121847d05a4ccef68244dadf82bfa331 | Vendor (CNA) |
| Linux Linux | 3e2129c67daca21043a26575108f6286c85e71f6 | Vendor (CNA) |
| Linux Linux | 4.14.299 | Vendor (CNA) |
| Linux Linux | 4.19.265 | Vendor (CNA) |
| Linux Linux | 4.9.333 | Vendor (CNA) |
| Linux Linux | 5.10.154 | Vendor (CNA) |
| Linux Linux | 5.15.78 | Vendor (CNA) |
| Linux Linux | 5.20 | Vendor (CNA) |
| Linux Linux | 5.4.224 | Vendor (CNA) |
| Linux Linux | 5b46adfbee1e429f33b10a88d6c00fa88f3d6c77 | Vendor (CNA) |
| Linux Linux | a601e5eded33bb88b8a42743db8fef3ad41dd97e | Vendor (CNA) |
| Linux Linux | b13be5e852b03f376058027e462fad4230240891 | Vendor (CNA) |
| Linux Linux | bbc03d74e641e824754443b908454ca9e203773e | Vendor (CNA) |
| Linux Linux | e97c089d7a49f67027395ddf70bf327eeac2611e | Vendor (CNA) |
| Linux Linux | f06186e5271b980bac03f5c97276ed0146ddc9b0 | Vendor (CNA) |
| debian:linux | 6.0.8-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/3e2129c67daca21043a26575108f6286c85e71f6
- git.kernel.org/stable/c/5b46adfbee1e429f33b10a88d6c00fa88f3d6c77
- git.kernel.org/stable/c/a601e5eded33bb88b8a42743db8fef3ad41dd97e
- git.kernel.org/stable/c/b13be5e852b03f376058027e462fad4230240891
- git.kernel.org/stable/c/bbc03d74e641e824754443b908454ca9e203773e
- git.kernel.org/stable/c/e97c089d7a49f67027395ddf70bf327eeac2611e
- git.kernel.org/stable/c/f06186e5271b980bac03f5c97276ed0146ddc9b0
Vendor advisories and official records. Exploit/PoC links are deliberately left out.