CVE-2024-46743

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2024-09-18. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-42004 (ENISA EUVD) · GHSA-jvc3-w86j-mcg3 (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

of/irq: Prevent device address out-of-bounds read in interrupt map walk

When of_irq_parse_raw() is invoked with a device address smaller than the interrupt parent node (from #address-cells property), KASAN detects the following out-of-bounds read when populating the initial match table (dyndbg="func of_irq_parse_* +p"):

OF: of_irq_parse_one: dev=/soc@0/picasso/watchdog, index=0 OF: parent=/soc@0/pci@878000000000/gpio0@17,0, intsize=2 OF: intspec=4 OF: of_irq_parse_raw: ipar=/soc@0/pci@878000000000/gpio0@17,0, size=2 OF: -> addrsize=3 ================================================================== BUG: KASAN: slab-out-of-bounds in of_irq_parse_raw+0x2b8/0x8d0 Read of size 4 at addr ffffff81beca5608 by task bash/764

CPU: 1 PID: 764 Comm: bash Tainted: G O 6.1.67-484c613561-nokia_sm_arm64 #1 Hardware name: Unknown Unknown Product/Unknown Product, BIOS 2023.01-12.24.03-dirty 01/01/2023 Call trace: dump_backtrace+0xdc/0x130 show_stack+0x1c/0x30 dump_stack_lvl+0x6c/0x84 print_report+0x150/0x448 kasan_report+0x98/0x140 __asan_load4+0x78/0xa0 of_irq_parse_raw+0x2b8/0x8d0 of_irq_parse_one+0x24c/0x270 parse_interrupts+0xc0/0x120 of_fwnode_add_links+0x100/0x2d0 fw_devlink_parse_fwtree+0x64/0xc0 device_add+0xb38/0xc30 of_device_add+0x64/0x90 of_platform_device_create_pdata+0xd0/0x170 of_platform_bus_create+0x244/0x600 of_platform_notify+0x1b0/0x254 blocking_notifier_call_chain+0x9c/0xd0 __of_changeset_entry_notify+0x1b8/0x230 __of_changeset_apply_notify+0x54/0xe4 of_overlay_fdt_apply+0xc04/0xd94 ...

The buggy address belongs to the object at ffffff81beca5600 which belongs to the cache kmalloc-128 of size 128 The buggy address is located 8 bytes inside of 128-byte region [ffffff81beca5600, ffffff81beca5680)

The buggy address belongs to the physical page: page:00000000230d3d03 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1beca4 head:00000000230d3d03 order:1 compound_mapcount:0 compound_pincount:0 flags: 0x8000000000010200(slab|head|zone=2) raw: 8000000000010200 0000000000000000 dead000000000122 ffffff810000c300 raw: 0000000000000000 0000000000200020 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffffff81beca5500: 04 fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffffff81beca5580: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >ffffff81beca5600: 00 fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ^ ffffff81beca5680: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffffff81beca5700: 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc fc ================================================================== OF: -> got it !

Prevent the out-of-bounds read by copying the device address into a buffer of sufficient size.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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 available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
21st
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 (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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, and whom BOD 26-04 binds: 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 available. Apply it within your standard update timelines.

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.

The score's inputs: 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

September 18, 2024

Last Modified

October 15, 2026

Advisory Details (8)

Auto-updated Aug 5, 2026
Patch available.
Web page

of/irq: Prevent device address out-of-bounds read in interrupt map walk - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b739dffa5d570b411d4bdf4bb9b8dfd6b7d72305
Web page

of/irq: Prevent device address out-of-bounds read in interrupt map walk - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bf68acd840b6a5bfd3777e0d5aaa204db6b461a9
Web page

of/irq: Prevent device address out-of-bounds read in interrupt map walk - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ead730af11ee7da107f16fc77995613c58d292d
Web page

of/irq: Prevent device address out-of-bounds read in interrupt map walk - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ff351ea12e918db1373b915c4c268815929cbe5
Web page

of/irq: Prevent device address out-of-bounds read in interrupt map walk - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/baaf26723beab3a04da578d3008be3544f83758f
Web page

of/irq: Prevent device address out-of-bounds read in interrupt map walk - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9d1e9f0876b03d74d44513a0ed3ed15ef8f2fed5
Web page

of/irq: Prevent device address out-of-bounds read in interrupt map walk - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/defcaa426ba0bc89ffdafb799d2e50b52f74ffc4
Web page

of/irq: Prevent device address out-of-bounds read in interrupt map walk - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d2a79494d8a5262949736fb2c3ac44d20a51b0d8

Vendor Advisories for CVE-2024-46743(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(22)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-bluefield (5.4.0.1094.90) @ focal2026-10-21ubuntu
ubuntulinux-tools-oracle-edge (5.4.0.1134.143~18.04.1) @ bionic2026-10-21ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1054 (5.4.0-1054.58) @ focal2026-10-21ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1038.42) @ jammy2026-10-21ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1119.149) @ focal2026-10-21ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.231.215) @ bionic2026-10-21ubuntu
ubuntulinux-tools-iot (5.4.0.1044.42) @ focal2026-10-21ubuntu
ubuntulinux-tools-azure (4.15.0.1183.198~14.04.1) @ trusty2026-10-21ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1067.67) @ jammy2026-10-21ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.261.267) @ xenial2026-10-21ubuntu
ubuntulinux-virtual-hwe-24.04 (6.8.0-50.51) @ noble2026-10-21ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1019.21.1) @ noble2026-10-21ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-50.51~22.04.1) @ jammy2026-10-21ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1078.87~20.04.1) @ focal2026-10-21ubuntu
ubuntulinux-tools-azure (6.8.0-1020.23) @ noble2026-10-21ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1072.72) @ jammy2026-10-21ubuntu
ubuntulinux-tools-oracle (4.15.0.1137.148~16.04.1) @ xenial2026-10-21ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1075.73) @ jammy2026-10-21ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.200.196) @ focal2026-10-21ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1002.4) @ noble2026-10-21ubuntu
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 4.19.322 (fixes >=2.6.18)—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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (43 versions)
  • every version up to 5.10.226-1: fixed in 5.10.226-1
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1
  • every version up to 6.1.119-1~deb11u1: fixed in 6.1.119-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (29 versions)
  • every version up to 6.1.112-1: fixed in 6.1.112-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.10.11-1: fixed in 6.10.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.10.11-1: fixed in 6.10.11-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(20)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-46743?
CVE-2024-46743 is a high-severity vulnerability; its CVE record was published on September 18, 2024. In the Linux kernel, the following vulnerability has been resolved: of/irq: Prevent device address out-of-bounds read in interrupt map walk When of_irq_parse_raw() is invoked with a device address smaller than the interrupt parent node (from #address-cells property), KASAN detects the following…
When was the CVE record for CVE-2024-46743 published?
The CVE record for CVE-2024-46743 was published on September 18, 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 October 15, 2026; the record at its source may have been updated since.
Is CVE-2024-46743 actively exploited?
CVE-2024-46743 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-46743?
CVE-2024-46743 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2024-46743?
A fix for CVE-2024-46743 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-46743 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-46743

Explore →

Is Your Infrastructure Affected by CVE-2024-46743?

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

Book a Demo →Browse All CVEs