CVE-2021-46957

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2024-02-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

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

riscv/kprobe: fix kernel panic when invoking sys_read traced by kprobe

The execution of sys_read end up hitting a BUG_ON() in __find_get_block after installing kprobe at sys_read, the BUG message like the following:

[ 65.708663] ------------[ cut here ]------------ [ 65.709987] kernel BUG at fs/buffer.c:1251! [ 65.711283] Kernel BUG [#1] [ 65.712032] Modules linked in: [ 65.712925] CPU: 0 PID: 51 Comm: sh Not tainted 5.12.0-rc4 #1 [ 65.714407] Hardware name: riscv-virtio,qemu (DT) [ 65.715696] epc : __find_get_block+0x218/0x2c8 [ 65.716835] ra : __getblk_gfp+0x1c/0x4a [ 65.717831] epc : ffffffe00019f11e ra : ffffffe00019f56a sp : ffffffe002437930 [ 65.719553] gp : ffffffe000f06030 tp : ffffffe0015abc00 t0 : ffffffe00191e038 [ 65.721290] t1 : ffffffe00191e038 t2 : 000000000000000a s0 : ffffffe002437960 [ 65.723051] s1 : ffffffe00160ad00 a0 : ffffffe00160ad00 a1 : 000000000000012a [ 65.724772] a2 : 0000000000000400 a3 : 0000000000000008 a4 : 0000000000000040 [ 65.726545] a5 : 0000000000000000 a6 : ffffffe00191e000 a7 : 0000000000000000 [ 65.728308] s2 : 000000000000012a s3 : 0000000000000400 s4 : 0000000000000008 [ 65.730049] s5 : 000000000000006c s6 : ffffffe00240f800 s7 : ffffffe000f080a8 [ 65.731802] s8 : 0000000000000001 s9 : 000000000000012a s10: 0000000000000008 [ 65.733516] s11: 0000000000000008 t3 : 00000000000003ff t4 : 000000000000000f [ 65.734434] t5 : 00000000000003ff t6 : 0000000000040000 [ 65.734613] status: 0000000000000100 badaddr: 0000000000000000 cause: 0000000000000003 [ 65.734901] Call Trace: [ 65.735076] [] __find_get_block+0x218/0x2c8 [ 65.735417] [] __ext4_get_inode_loc+0xb2/0x2f6 [ 65.735618] [] ext4_get_inode_loc+0x3a/0x8a [ 65.735802] [] ext4_reserve_inode_write+0x2e/0x8c [ 65.735999] [] __ext4_mark_inode_dirty+0x4c/0x18e [ 65.736208] [] ext4_dirty_inode+0x46/0x66 [ 65.736387] [] __mark_inode_dirty+0x12c/0x3da [ 65.736576] [] touch_atime+0x146/0x150 [ 65.736748] [] filemap_read+0x234/0x246 [ 65.736920] [] generic_file_read_iter+0xc0/0x114 [ 65.737114] [] ext4_file_read_iter+0x42/0xea [ 65.737310] [] new_sync_read+0xe2/0x15a [ 65.737483] [] vfs_read+0xca/0xf2 [ 65.737641] [] ksys_read+0x5e/0xc8 [ 65.737816] [] sys_read+0xe/0x16 [ 65.737973] [] ret_from_syscall+0x0/0x2 [ 65.738858] ---[ end trace fe93f985456c935d ]---

A simple reproducer looks like: echo 'p:myprobe sys_read fd=%a0 buf=%a1 count=%a2' > /sys/kernel/debug/tracing/kprobe_events echo 1 > /sys/kernel/debug/tracing/events/kprobes/myprobe/enable cat /sys/kernel/debug/tracing/trace

Here's what happens to hit that BUG_ON():

1) After installing kprobe at entry of sys_read, the first instruction is replaced by 'ebreak' instruction on riscv64 platform.

2) Once kernel reach the 'ebreak' instruction at the entry of sys_read, it trap into the riscv breakpoint handler, where it do something to setup for coming single-step of origin instruction, including backup the 'sstatus' in pt_regs, followed by disable interrupt during single stepping via clear 'SIE' bit of 'sstatus' in pt_regs.

3) Then kernel restore to the instruction slot contains two instructions, one is original instruction at entry of sys_read, the other is 'ebreak'. Here it trigger a 'Instruction page fault' exception (value at 'scause' is '0xc'), if PF is not filled into PageTabe for that slot yet.

4) Again kernel trap into page fault exception handler, where it choose different policy according to the state of running kprobe. Because afte 2) the state is KPROBE_HIT_SS, so kernel reset the current kp ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
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)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

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

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

February 27, 2024

Last Modified

March 14, 2025

References (2)

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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 94 of 180 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 86 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2021-46957?
CVE-2021-46957 is a medium-severity vulnerability; its CVE record was published on February 27, 2024. In the Linux kernel, the following vulnerability has been resolved: riscv/kprobe: fix kernel panic when invoking sys_read traced by kprobe The execution of sysread end up hitting a BUGON() in findgetblock after installing kprobe at sys_read, the BUG message like the following: [ 65.708663]…
When was the CVE record for CVE-2021-46957 published?
The CVE record for CVE-2021-46957 was published on February 27, 2024. 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 March 14, 2025; the record at its source may have been updated since.
Is CVE-2021-46957 actively exploited?
CVE-2021-46957 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).
What is the CVSS score of CVE-2021-46957?
CVE-2021-46957 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2021-46957?
A fix for CVE-2021-46957 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2021-46957

Explore →

Is Your Infrastructure Affected by CVE-2021-46957?

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

Book a Demo →Browse All CVEs