CVE-2022-50647

UNRATEDCVSS · not yet scored

Also known asEUVD-2022-55709 (ENISA EUVD) · GHSA-gvvr-vj5m-jq76 (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 9, 2025

Last Modified

April 15, 2026

References (6)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.4.220 (fixes >=4.15.0)—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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (22 versions)
  • every version up to 5.10.158-1: fixed in 5.10.158-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.3-1: fixed in 6.0.3-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.3-1: fixed in 6.0.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.3-1: fixed in 6.0.3-1
—

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 236 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 138 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(4)

What is CVE-2022-50647?
CVE-2022-50647 is a vulnerability whose severity is not yet rated; its CVE record was 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 the CVE record for CVE-2022-50647 published?
The CVE record for CVE-2022-50647 was published on December 9, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2022-50647 actively exploited?
CVE-2022-50647 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2022-50647?
A fix for CVE-2022-50647 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs