Bug 2453458 (CVE-2026-5265) - CVE-2026-5265 ovn: ovn: Heap Over-Read in ICMP Error Response Generation - security issue
Summary: CVE-2026-5265 ovn: ovn: Heap Over-Read in ICMP Error Response Generation - se...
Keywords:
Status: NEW
Alias: CVE-2026-5265
Deadline: 2026-04-06
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-03-31 17:41 UTC by OSIDB Bzimport
Modified: 2026-04-29 12:46 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:11694 0 None None None 2026-04-29 12:41:31 UTC
Red Hat Product Errata RHSA-2026:11695 0 None None None 2026-04-29 12:41:37 UTC
Red Hat Product Errata RHSA-2026:11696 0 None None None 2026-04-29 12:41:57 UTC
Red Hat Product Errata RHSA-2026:11698 0 None None None 2026-04-29 12:41:46 UTC
Red Hat Product Errata RHSA-2026:11700 0 None None None 2026-04-29 12:46:46 UTC
Red Hat Product Errata RHSA-2026:11701 0 None None None 2026-04-29 12:42:51 UTC
Red Hat Product Errata RHSA-2026:11702 0 None None None 2026-04-29 12:46:26 UTC

Description OSIDB Bzimport 2026-03-31 17:41:34 UTC 
When generating an ICMP Destination Unreachable or Packet Too Big response, the handler copies a portion of the original packet into the ICMP error body using the IP header's self-declared total length (ip_tot_len for IPv4, ip6_plen for IPv6) without validating it against the actual packet buffer size. A VM can send a short packet with an inflated IP length field that triggers an ICMP error (e.g., by hitting a reject ACL), causing ovn-controller to read heap memory beyond the valid packet data and include it in the ICMP response sent back to the VM.
Comment 2 errata-xmlrpc 2026-04-29 12:41:30 UTC 
This issue has been addressed in the following products:

  Fast Datapath for Red Hat Enterprise Linux 8

Via RHSA-2026:11694 https://access.redhat.com/errata/RHSA-2026:11694
Comment 3 errata-xmlrpc 2026-04-29 12:41:36 UTC 
This issue has been addressed in the following products:

  Fast Datapath for Red Hat Enterprise Linux 8

Via RHSA-2026:11695 https://access.redhat.com/errata/RHSA-2026:11695
Comment 4 errata-xmlrpc 2026-04-29 12:41:45 UTC 
This issue has been addressed in the following products:

  Fast Datapath for Red Hat Enterprise Linux 9

Via RHSA-2026:11698 https://access.redhat.com/errata/RHSA-2026:11698
Comment 5 errata-xmlrpc 2026-04-29 12:41:55 UTC 
This issue has been addressed in the following products:

  Fast Datapath for Red Hat Enterprise Linux 9

Via RHSA-2026:11696 https://access.redhat.com/errata/RHSA-2026:11696
Comment 6 errata-xmlrpc 2026-04-29 12:42:50 UTC 
This issue has been addressed in the following products:

  Fast Datapath for Red Hat Enterprise Linux 9

Via RHSA-2026:11701 https://access.redhat.com/errata/RHSA-2026:11701
Comment 7 errata-xmlrpc 2026-04-29 12:46:24 UTC 
This issue has been addressed in the following products:

  Fast Datapath for Red Hat Enterprise Linux 9

Via RHSA-2026:11702 https://access.redhat.com/errata/RHSA-2026:11702
Comment 8 errata-xmlrpc 2026-04-29 12:46:45 UTC 
This issue has been addressed in the following products:

  Fast Datapath for Red Hat Enterprise Linux 9

Via RHSA-2026:11700 https://access.redhat.com/errata/RHSA-2026:11700
Note You need to log in before you can comment on or make changes to this bug.