CVE-2022-50647

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

RISC-V: Make port I/O string accessors actually work

Fix port I/O string accessors such as insb', outsb', etc. which use the physical PCI port I/O address rather than the corresponding memory mapping to get at the requested location, which in turn breaks at least accesses made by our parport driver to a PCIe parallel port such as:

PCI parallel port detected: 1415:c118, I/O at 0x1000(0x1008), IRQ 20 parport0: PC-style at 0x1000 (0x1008), irq 20, using FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP]

causing a memory access fault:

Unable to handle kernel access to user memory without uaccess routines at virtual address 0000000000001008 Oops [#1] Modules linked in: CPU: 1 PID: 350 Comm: cat Not tainted 6.0.0-rc2-00283-g10d4879f9ef0-dirty #23 Hardware name: SiFive HiFive Unmatched A00 (DT) epc : parport_pc_fifo_write_block_pio+0x266/0x416 ra : parport_pc_fifo_write_block_pio+0xb4/0x416 epc : ffffffff80542c3e ra : ffffffff80542a8c sp : ffffffd88899fc60 gp : ffffffff80fa2700 tp : ffffffd882b1e900 t0 : ffffffd883d0b000 t1 : ffffffffff000002 t2 : 4646393043330a38 s0 : ffffffd88899fcf0 s1 : 0000000000001000 a0 : 0000000000000010 a1 : 0000000000000000 a2 : ffffffd883d0a010 a3 : 0000000000000023 a4 : 00000000ffff8fbb a5 : ffffffd883d0a001 a6 : 0000000100000000 a7 : ffffffc800000000 s2 : ffffffffff000002 s3 : ffffffff80d28880 s4 : ffffffff80fa1f50 s5 : 0000000000001008 s6 : 0000000000000008 s7 : ffffffd883d0a000 s8 : 0004000000000000 s9 : ffffffff80dc1d80 s10: ffffffd8807e4000 s11: 0000000000000000 t3 : 00000000000000ff t4 : 393044410a303930 t5 : 0000000000001000 t6 : 0000000000040000 status: 0000000200000120 badaddr: 0000000000001008 cause: 000000000000000f [] parport_pc_compat_write_block_pio+0xfe/0x200 [] parport_write+0x46/0xf8 [] lp_write+0x158/0x2d2 [] vfs_write+0x8e/0x2c2 [] ksys_write+0x52/0xc2 [] sys_write+0xe/0x16 [] ret_from_syscall+0x0/0x2 ---[ end trace 0000000000000000 ]---

For simplicity address the problem by adding PCI_IOBASE to the physical address requested in the respective wrapper macros only, observing that the raw accessors such as __insb', __outsb', etc. are not supposed to be used other than by said macros. Remove the cast to long' that is no longer needed on addr' now that it is used as an offset from PCI_IOBASE and add parentheses around `addr' needed for predictable evaluation in macro expansion. No need to make said adjustments in separate changes given that current code is gravely broken and does not ever work.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

December 9, 2025

Last Modified

April 15, 2026

References (6)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.4.220—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Data Freshness Timeline

(refreshed 7× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 149 total refreshes for this CVE.

  1. 2026-08-05 19:15 UTCEPSS rescore
  2. 2026-08-04 15:07 UTCEPSS rescore
  3. 2026-08-04 10:35 UTCEPSS rescore
  4. 2026-08-03 10:33 UTCEPSS rescore
  5. 2026-08-02 02:24 UTCEPSS rescore
  6. 2026-07-30 16:25 UTCEPSS rescore
  7. 2026-07-30 01:28 UTCEPSS rescore
  8. 2026-07-28 15:34 UTCEPSS rescore
  9. 2026-07-27 05:39 UTCOSV refresh
  10. 2026-07-26 14:52 UTCEPSS rescore
  11. 2026-07-26 14:52 UTCEPSS rescore
  12. 2026-07-25 14:16 UTCEPSS rescore
  13. 2026-07-24 14:15 UTCEPSS rescore
  14. 2026-07-23 14:16 UTCEPSS rescore
  15. 2026-07-23 14:16 UTCEPSS rescore
  16. 2026-07-23 02:17 UTCEG score recompute
  17. 2026-07-22 23:04 UTCEG score recompute
  18. 2026-07-22 14:06 UTCEPSS rescore
  19. 2026-07-22 14:06 UTCEPSS rescore
  20. 2026-07-21 15:23 UTCEPSS rescore
  21. 2026-07-21 15:23 UTCEPSS rescore
  22. 2026-07-20 17:05 UTCEPSS rescore
  23. 2026-07-19 14:29 UTCEPSS rescore
  24. 2026-07-19 14:29 UTCEPSS rescore
  25. 2026-07-19 02:27 UTCEPSS rescore
Show 75 more
  1. 2026-07-19 02:27 UTCEPSS rescore
  2. 2026-07-18 10:03 UTCEPSS rescore
  3. 2026-07-18 10:03 UTCEPSS rescore
  4. 2026-07-16 17:00 UTCEPSS rescore
  5. 2026-07-15 16:56 UTCEPSS rescore
  6. 2026-07-15 16:56 UTCEPSS rescore
  7. 2026-07-15 01:58 UTCEPSS rescore
  8. 2026-07-15 01:58 UTCEPSS rescore
  9. 2026-07-13 22:28 UTCEPSS rescore
  10. 2026-07-13 22:28 UTCEPSS rescore
  11. 2026-07-13 06:11 UTCEPSS rescore
  12. 2026-07-13 06:11 UTCEPSS rescore
  13. 2026-07-12 05:44 UTCEPSS rescore
  14. 2026-07-11 08:25 UTCEPSS rescore
  15. 2026-07-11 08:25 UTCEPSS rescore
  16. 2026-07-10 00:17 UTCOSV refresh
  17. 2026-07-09 19:08 UTCEPSS rescore
  18. 2026-07-08 15:13 UTCEPSS rescore
  19. 2026-07-07 13:44 UTCEPSS rescore
  20. 2026-07-06 16:25 UTCEPSS rescore
  21. 2026-07-06 02:21 UTCEPSS rescore
  22. 2026-07-05 02:28 UTCEPSS rescore
  23. 2026-07-04 06:29 UTCEPSS rescore
  24. 2026-07-01 15:04 UTCEPSS rescore
  25. 2026-06-30 23:21 UTCEPSS rescore
  26. 2026-06-30 23:20 UTCEPSS rescore
  27. 2026-06-29 14:04 UTCEPSS rescore
  28. 2026-06-28 14:06 UTCEPSS rescore
  29. 2026-06-28 04:54 UTCEPSS rescore
  30. 2026-06-28 04:54 UTCEPSS rescore
  31. 2026-06-27 03:07 UTCEPSS rescore
  32. 2026-06-27 03:07 UTCEPSS rescore
  33. 2026-06-25 13:48 UTCEPSS rescore
  34. 2026-06-25 13:48 UTCEPSS rescore
  35. 2026-06-24 14:03 UTCEPSS rescore
  36. 2026-06-24 14:03 UTCEPSS rescore
  37. 2026-06-23 21:31 UTCEPSS rescore
  38. 2026-06-23 21:31 UTCEPSS rescore
  39. 2026-06-22 14:24 UTCEPSS rescore
  40. 2026-06-21 14:55 UTCEPSS rescore
  41. 2026-06-21 14:55 UTCEPSS rescore
  42. 2026-06-21 11:01 UTCOSV refresh
  43. 2026-06-21 01:58 UTCEPSS rescore
  44. 2026-06-21 01:58 UTCEPSS rescore
  45. 2026-06-19 19:24 UTCEPSS rescore
  46. 2026-06-19 19:24 UTCEPSS rescore
  47. 2026-06-18 17:51 UTCEPSS rescore
  48. 2026-06-18 17:51 UTCEPSS rescore
  49. 2026-06-17 17:51 UTCEPSS rescore
  50. 2026-06-17 17:51 UTCEPSS rescore
  51. 2026-06-16 17:51 UTCEPSS rescore
  52. 2026-06-16 17:51 UTCEPSS rescore
  53. 2026-06-15 17:47 UTCEPSS rescore
  54. 2026-06-14 23:16 UTCEPSS rescore
  55. 2026-06-13 22:59 UTCEPSS rescore
  56. 2026-06-12 23:10 UTCEPSS rescore
  57. 2026-06-12 23:10 UTCEPSS rescore
  58. 2026-06-11 13:58 UTCEPSS rescore
  59. 2026-06-11 13:58 UTCEPSS rescore
  60. 2026-06-10 13:21 UTCEPSS rescore
  61. 2026-06-10 13:21 UTCEPSS rescore
  62. 2026-06-08 14:15 UTCEPSS rescore
  63. 2026-06-08 14:15 UTCEPSS rescore
  64. 2026-06-07 15:23 UTCEPSS rescore
  65. 2026-06-07 15:23 UTCEPSS rescore
  66. 2026-06-06 13:46 UTCEPSS rescore
  67. 2026-06-06 13:46 UTCEPSS rescore
  68. 2026-06-05 22:46 UTCEPSS rescore
  69. 2026-06-05 22:46 UTCEPSS rescore
  70. 2026-06-05 06:09 UTCEPSS rescore
  71. 2026-06-05 06:09 UTCEPSS rescore
  72. 2026-06-04 13:11 UTCEPSS rescore
  73. 2026-06-02 20:12 UTCEPSS rescore
  74. 2026-06-02 20:12 UTCEPSS rescore
  75. 2026-06-02 02:39 UTCOSV refresh

Related CVEs(same product)

Frequently asked(4)

What is CVE-2022-50647?
CVE-2022-50647 is a publicly disclosed vulnerability published on December 9, 2025. In the Linux kernel, the following vulnerability has been resolved: RISC-V: Make port I/O string accessors actually work Fix port I/O string accessors such as insb', outsb', etc. which use the physical PCI port I/O address rather than the corresponding memory mapping to get at the requested…
When was CVE-2022-50647 disclosed?
CVE-2022-50647 was first published in the National Vulnerability Database on December 9, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50647 actively exploited?
CVE-2022-50647 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.9% of all scored CVEs.
How do I remediate CVE-2022-50647?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50647, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-50647

Explore →

Is Your Infrastructure Affected by CVE-2022-50647?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs