Bug 2467822 (CVE-2026-33811) - CVE-2026-33811 net: golang: Go net package: Denial of Service via long CNAME response in LookupCNAME
Summary: CVE-2026-33811 net: golang: Go net package: Denial of Service via long CNAME ...
Keywords:
Status: NEW
Alias: CVE-2026-33811
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-07 20:01 UTC by OSIDB Bzimport
Modified: 2026-07-09 12:43 UTC (History)
157 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:22112 0 None None None 2026-06-01 01:04:30 UTC
Red Hat Product Errata RHSA-2026:22120 0 None None None 2026-06-01 00:44:00 UTC
Red Hat Product Errata RHSA-2026:22121 0 None None None 2026-06-01 01:00:49 UTC
Red Hat Product Errata RHSA-2026:34357 0 None None None 2026-07-01 18:36:14 UTC
Red Hat Product Errata RHSA-2026:34359 0 None None None 2026-07-01 19:21:09 UTC
Red Hat Product Errata RHSA-2026:35832 0 None None None 2026-07-06 03:06:07 UTC
Red Hat Product Errata RHSA-2026:36617 0 None None None 2026-07-08 09:01:16 UTC
Red Hat Product Errata RHSA-2026:36776 0 None None None 2026-07-08 16:19:57 UTC
Red Hat Product Errata RHSA-2026:36796 0 None None None 2026-07-08 15:51:00 UTC

Description OSIDB Bzimport 2026-05-07 20:01:57 UTC 
When using LookupCNAME with the cgo DNS resolver, a very long CNAME response can trigger a double-free of C memory and a crash.
Comment 2 errata-xmlrpc 2026-06-01 00:43:52 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:22120 https://access.redhat.com/errata/RHSA-2026:22120
Comment 3 errata-xmlrpc 2026-06-01 01:00:42 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:22121 https://access.redhat.com/errata/RHSA-2026:22121
Comment 4 errata-xmlrpc 2026-06-01 01:04:24 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:22112 https://access.redhat.com/errata/RHSA-2026:22112
Comment 5 errata-xmlrpc 2026-07-01 18:36:06 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:34357 https://access.redhat.com/errata/RHSA-2026:34357
Comment 6 errata-xmlrpc 2026-07-01 19:21:00 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:34359 https://access.redhat.com/errata/RHSA-2026:34359
Comment 10 errata-xmlrpc 2026-07-06 03:05:58 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:35832 https://access.redhat.com/errata/RHSA-2026:35832
Comment 13 errata-xmlrpc 2026-07-08 09:01:08 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:36617 https://access.redhat.com/errata/RHSA-2026:36617
Comment 14 errata-xmlrpc 2026-07-08 15:50:51 UTC 
This issue has been addressed in the following products:

  RHEM 1.0 for RHEL 9

Via RHSA-2026:36796 https://access.redhat.com/errata/RHSA-2026:36796
Comment 15 errata-xmlrpc 2026-07-08 16:19:49 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

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