[BACK]Return to errata66.html CVS log [TXT][DIR] Up to [local] / www

Annotation of www/errata66.html, Revision 1.39

1.1       deraadt     1: <!doctype html>
                      2: <html lang=en id=errata>
                      3: <meta charset=utf-8>
                      4:
                      5: <title>OpenBSD 6.6 Errata</title>
                      6: <meta name="description" content="the OpenBSD errata page">
                      7: <meta name="viewport" content="width=device-width, initial-scale=1">
                      8: <link rel="stylesheet" type="text/css" href="openbsd.css">
                      9: <link rel="canonical" href="https://www.openbsd.org/errata66.html">
                     10:
                     11: <!--
                     12:                        IMPORTANT REMINDER
                     13:        IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
                     14: -->
                     15:
                     16: <h2 id=OpenBSD>
                     17: <a href="index.html">
                     18: <i>Open</i><b>BSD</b></a>
                     19: 6.6 Errata
                     20: </h2>
                     21: <hr>
                     22:
                     23: For errata on a certain release, click below:<br>
1.21      schwarze   24: <a href="errata20.html">2.0</a>,
1.1       deraadt    25: <a href="errata21.html">2.1</a>,
                     26: <a href="errata22.html">2.2</a>,
                     27: <a href="errata23.html">2.3</a>,
                     28: <a href="errata24.html">2.4</a>,
                     29: <a href="errata25.html">2.5</a>,
                     30: <a href="errata26.html">2.6</a>,
                     31: <a href="errata27.html">2.7</a>,
                     32: <a href="errata28.html">2.8</a>,
                     33: <a href="errata29.html">2.9</a>,
                     34: <a href="errata30.html">3.0</a>,
                     35: <a href="errata31.html">3.1</a>,
                     36: <a href="errata32.html">3.2</a>,
                     37: <a href="errata33.html">3.3</a>,
                     38: <a href="errata34.html">3.4</a>,
                     39: <a href="errata35.html">3.5</a>,
1.21      schwarze   40: <br>
1.1       deraadt    41: <a href="errata36.html">3.6</a>,
                     42: <a href="errata37.html">3.7</a>,
                     43: <a href="errata38.html">3.8</a>,
                     44: <a href="errata39.html">3.9</a>,
                     45: <a href="errata40.html">4.0</a>,
                     46: <a href="errata41.html">4.1</a>,
                     47: <a href="errata42.html">4.2</a>,
                     48: <a href="errata43.html">4.3</a>,
                     49: <a href="errata44.html">4.4</a>,
                     50: <a href="errata45.html">4.5</a>,
                     51: <a href="errata46.html">4.6</a>,
                     52: <a href="errata47.html">4.7</a>,
                     53: <a href="errata48.html">4.8</a>,
                     54: <a href="errata49.html">4.9</a>,
                     55: <a href="errata50.html">5.0</a>,
                     56: <a href="errata51.html">5.1</a>,
1.21      schwarze   57: <br>
1.1       deraadt    58: <a href="errata52.html">5.2</a>,
                     59: <a href="errata53.html">5.3</a>,
                     60: <a href="errata54.html">5.4</a>,
                     61: <a href="errata55.html">5.5</a>,
                     62: <a href="errata56.html">5.6</a>,
                     63: <a href="errata57.html">5.7</a>,
                     64: <a href="errata58.html">5.8</a>,
                     65: <a href="errata59.html">5.9</a>,
                     66: <a href="errata60.html">6.0</a>,
                     67: <a href="errata61.html">6.1</a>,
                     68: <a href="errata62.html">6.2</a>,
                     69: <a href="errata63.html">6.3</a>,
                     70: <a href="errata64.html">6.4</a>,
1.22      deraadt    71: <a href="errata65.html">6.5</a>,
1.39    ! deraadt    72: <a href="errata67.html">6.7</a>,
        !            73: <a href="errata68.html">6.8</a>.
1.1       deraadt    74: <hr>
                     75:
                     76: <p>
                     77: Patches for the OpenBSD base system are distributed as unified diffs.
                     78: Each patch is cryptographically signed with the
                     79: <a href="https://man.openbsd.org/OpenBSD-6.6/signify.1">signify(1)</a> tool and contains
                     80: usage instructions.
                     81: All the following patches are also available in one
                     82: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6.tar.gz">tar.gz file</a>
                     83: for convenience.
                     84:
                     85: <p>
                     86: Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
                     87: utility can be used to apply binary updates on the following architectures:
                     88: amd64, i386, arm64.
                     89:
                     90: <p>
                     91: Patches for supported releases are also incorporated into the
                     92: <a href="stable.html">-stable branch</a>, which is maintained for one year
                     93: after release.
                     94:
                     95: <hr>
                     96:
                     97: <ul>
                     98:
1.2       tj         99: <li id="p001_bpf">
                    100: <strong>001: RELIABILITY FIX: October 28, 2019</strong>
                    101: &nbsp; <i>All architectures</i>
                    102: <br>
                    103: bpf(4) has a race condition during device removal.
                    104: <br>
                    105: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/001_bpf.patch.sig">
                    106: A source code patch exists which remedies this problem.</a>
                    107: <p>
                    108:
                    109: <li id="p002_ber">
                    110: <strong>002: RELIABILITY FIX: October 28, 2019</strong>
                    111: &nbsp; <i>All architectures</i>
                    112: <br>
                    113: Various third party applications may crash due to symbol collision.
                    114: <br>
                    115: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/002_ber.patch.sig">
                    116: A source code patch exists which remedies this problem.</a>
                    117: <p>
1.1       deraadt   118:
1.4       tj        119: <li id="p003_bgpd">
                    120: <strong>003: RELIABILITY FIX: October 31, 2019</strong>
                    121: &nbsp; <i>All architectures</i>
                    122: <br>
                    123: bgpd(8) can crash on nexthop changes or during startup in certain
                    124: configurations.
                    125: <br>
                    126: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/003_bgpd.patch.sig">
                    127: A source code patch exists which remedies this problem.</a>
                    128: <p>
                    129:
1.5       tj        130: <li id="p004_net80211">
                    131: <strong>004: RELIABILITY FIX: November 16, 2019</strong>
                    132: &nbsp; <i>All architectures</i>
                    133: <br>
                    134: The kernel could crash due to a NULL pointer dereference in net80211.
                    135: <br>
                    136: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/004_net80211.patch.sig">
                    137: A source code patch exists which remedies this problem.</a>
                    138: <p>
                    139:
                    140: <li id="p005_sysupgrade">
                    141: <strong>005: RELIABILITY FIX: November 16, 2019</strong>
                    142: &nbsp; <i>All architectures</i>
                    143: <br>
                    144: A new kernel may require newer firmware images when using sysupgrade.
                    145: <br>
                    146: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/005_sysupgrade.patch.sig">
                    147: A source code patch exists which remedies this problem.</a>
                    148: <p>
                    149:
                    150: <li id="p006_ifioctl">
                    151: <strong>006: SECURITY FIX: November 16, 2019</strong>
                    152: &nbsp; <i>All architectures</i>
                    153: <br>
                    154: A regular user could change some network interface parameters due
                    155: to missing checks in the ioctl(2) system call.
                    156: <br>
                    157: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/006_ifioctl.patch.sig">
                    158: A source code patch exists which remedies this problem.</a>
                    159: <p>
                    160:
1.6       tj        161: <li id="p007_inteldrm">
                    162: <strong>007: SECURITY FIX: November 22, 2019</strong>
                    163: &nbsp; <i>i386 and amd64</i>
                    164: <br>
                    165: A local user could cause the system to hang by reading specific
                    166: registers when Intel Gen8/Gen9 graphics hardware is in a low power state.
                    167: A local user could perform writes to memory that should be blocked with
                    168: Intel Gen9 graphics hardware.
                    169: <br>
                    170: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/007_inteldrm.patch.sig">
                    171: A source code patch exists which remedies this problem.</a>
                    172: <p>
                    173:
                    174: <li id="p008_mesa">
                    175: <strong>008: SECURITY FIX: November 22, 2019</strong>
                    176: &nbsp; <i>All architectures</i>
                    177: <br>
                    178: Shared memory regions used by some Mesa drivers had permissions which
                    179: allowed others to access that memory.
                    180: <br>
                    181: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/008_mesa.patch.sig">
                    182: A source code patch exists which remedies this problem.</a>
                    183: <p>
                    184:
1.7       tb        185: <li id="p009_mesaxlock">
                    186: <strong>009: SECURITY FIX: December 4, 2019</strong>
                    187: &nbsp; <i>All architectures</i>
                    188: <br>
                    189: Environment-provided paths are used for dlopen() in mesa, resulting in
                    190: escalation to the auth group in xlock(1).
                    191: <br>
                    192: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/009_mesaxlock.patch.sig">
                    193: A source code patch exists which remedies this problem.</a>
                    194: <p>
                    195:
                    196: <li id="p010_libcauth">
                    197: <strong>010: SECURITY FIX: December 4, 2019</strong>
                    198: &nbsp; <i>All architectures</i>
                    199: <br>
                    200: libc's authentication layer performed insufficient username validation.
                    201: <br>
                    202: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/010_libcauth.patch.sig">
                    203: A source code patch exists which remedies this problem.</a>
                    204: <p>
                    205:
                    206: <li id="p011_xenodm">
                    207: <strong>011: SECURITY FIX: December 4, 2019</strong>
                    208: &nbsp; <i>All architectures</i>
                    209: <br>
                    210: xenodm uses the libc authentication layer incorrectly.
                    211: <br>
                    212: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/011_xenodm.patch.sig">
                    213: A source code patch exists which remedies this problem.</a>
                    214: <p>
                    215:
1.8       tj        216: <li id="p012_suauth">
                    217: <strong>012: SECURITY FIX: December 8, 2019</strong>
                    218: &nbsp; <i>All architectures</i>
                    219: <br>
                    220: A user can log in with a different user's login class.
                    221: <br>
                    222: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/012_suauth.patch.sig">
                    223: A source code patch exists which remedies this problem.</a>
                    224: <p>
                    225:
1.9       tj        226: <li id="p013_ldso">
                    227: <strong>013: SECURITY FIX: December 11, 2019</strong>
                    228: &nbsp; <i>All architectures</i>
                    229: <br>
                    230: ld.so may fail to remove the LD_LIBRARY_PATH environment variable for
                    231: set-user-ID and set-group-ID executables in low memory conditions.
                    232: <br>
                    233: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/013_ldso.patch.sig">
                    234: A source code patch exists which remedies this problem.</a>
                    235: <p>
                    236:
1.10      tj        237: <li id="p014_eret">
                    238: <strong>014: SECURITY FIX: December 18, 2019</strong>
                    239: &nbsp; <i>arm64</i>
                    240: <br>
                    241: ARM64 CPUs speculatively execute instructions after ERET.
                    242: <br>
                    243: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/014_eret.patch.sig">
                    244: A source code patch exists which remedies this problem.</a>
                    245: <p>
                    246:
1.11      tj        247: <li id="p015_ftp">
                    248: <strong>015: SECURITY FIX: December 20, 2019</strong>
                    249: &nbsp; <i>All architectures</i>
                    250: <br>
                    251: ftp(1) will follow remote redirects to local files.
                    252: <br>
                    253: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/015_ftp.patch.sig">
                    254: A source code patch exists which remedies this problem.</a>
                    255: <p>
                    256:
                    257: <li id="p016_ripd">
                    258: <strong>016: SECURITY FIX: December 20, 2019</strong>
                    259: &nbsp; <i>All architectures</i>
                    260: <br>
                    261: ripd(8) fails to validate authentication lengths.
                    262: <br>
                    263: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/016_ripd.patch.sig">
                    264: A source code patch exists which remedies this problem.</a>
                    265: <p>
                    266:
1.12      tj        267: <li id="p017_inteldrmctx">
                    268: <strong>017: SECURITY FIX: January 17, 2020</strong>
                    269: &nbsp; <i>i386 and amd64</i>
                    270: <br>
                    271: Execution Unit state was not cleared on context switch with Intel Gen9
                    272: graphics hardware.
                    273: <br>
                    274: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/017_inteldrmctx.patch.sig">
                    275: A source code patch exists which remedies this problem.</a>
                    276: <p>
                    277:
1.13      tj        278: <li id="p018_smtpd_tls">
                    279: <strong>018: RELIABILITY FIX: January 30, 2020</strong>
                    280: &nbsp; <i>All architectures</i>
                    281: <br>
                    282: smtpd can crash on opportunistic TLS downgrade, causing a denial of service.
                    283: <br>
                    284: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/018_smtpd_tls.patch.sig">
                    285: A source code patch exists which remedies this problem.</a>
                    286: <p>
                    287:
                    288: <li id="p019_smtpd_exec">
                    289: <strong>019: SECURITY FIX: January 30, 2020</strong>
                    290: &nbsp; <i>All architectures</i>
                    291: <br>
                    292: An incorrect check allows an attacker to trick mbox delivery into executing
                    293: arbitrary commands as root and lmtp delivery into executing arbitrary commands
                    294: as an unprivileged user.
                    295: <br>
                    296: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/019_smtpd_exec.patch.sig">
                    297: A source code patch exists which remedies this problem.</a>
                    298: <p>
                    299:
1.14      tj        300: <li id="p020_vmm_pvclock">
                    301: <strong>020: SECURITY FIX: February 17, 2020</strong>
                    302: &nbsp; <i>amd64</i>
                    303: <br>
                    304: A missing range check in the vmm pvclock allows a guest to write
                    305: to host memory.
                    306: <br>
                    307: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/020_vmm_pvclock.patch.sig">
                    308: A source code patch exists which remedies this problem.</a>
                    309: <p>
                    310:
1.15      tj        311: <li id="p021_smtpd_envelope">
                    312: <strong>021: SECURITY FIX: February 24, 2020</strong>
                    313: &nbsp; <i>All architectures</i>
                    314: <br>
                    315: An out of bounds read in smtpd allows an attacker to inject arbitrary
                    316: commands into the envelope file which are then executed as root.
                    317: Separately, missing privilege revocation in smtpctl allows arbitrary
                    318: commands to be run with the _smtpq group.
                    319: <br>
                    320: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/021_smtpd_envelope.patch.sig">
                    321: A source code patch exists which remedies this problem.</a>
                    322: <p>
1.14      tj        323:
1.16      tj        324: <li id="p022_sysctl">
                    325: <strong>022: RELIABILITY FIX: March 10, 2020</strong>
                    326: &nbsp; <i>All architectures</i>
                    327: <br>
                    328: Missing input validation in sysctl(2) can be used to crash the kernel.
                    329: <br>
                    330: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/022_sysctl.patch.sig">
                    331: A source code patch exists which remedies this problem.</a>
                    332: <p>
                    333:
1.17      tj        334: <li id="p023_sosplice">
                    335: <strong>023: RELIABILITY FIX: March 13, 2020</strong>
                    336: &nbsp; <i>All architectures</i>
                    337: <br>
                    338: Local outbound UDP broadcast or multicast packets sent by a spliced
                    339: socket can crash the kernel.
                    340: <br>
                    341: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/023_sosplice.patch.sig">
                    342: A source code patch exists which remedies this problem.</a>
                    343: <p>
                    344:
1.18      tj        345: <li id="p024_dhcpd">
                    346: <strong>024: SECURITY FIX: April 7, 2020</strong>
                    347: &nbsp; <i>All architectures</i>
                    348: <br>
                    349: dhcpd could reference freed memory after releasing a lease with an
                    350: unusually long uid.
                    351: <br>
                    352: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/024_dhcpd.patch.sig">
                    353: A source code patch exists which remedies this problem.</a>
                    354: <p>
                    355:
1.19      tj        356: <li id="p025_drm">
                    357: <strong>025: SECURITY FIX: April 19, 2020</strong>
                    358: &nbsp; <i>i386, amd64, arm64, loongson, macppc, sparc64</i>
                    359: <br>
1.20      tj        360: There was an incorrect test for root in the DRM Linux compatibility code.
1.19      tj        361: <br>
                    362: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/025_drm.patch.sig">
                    363: A source code patch exists which remedies this problem.</a>
                    364: <p>
                    365:
1.23      tj        366: <li id="p026_ospfd_lsa">
                    367: <strong>026: RELIABILITY FIX: May 10, 2020</strong>
                    368: &nbsp; <i>All architectures</i>
                    369: <br>
                    370: ospfd could generate corrupt OSPF Router (Type 1) LSAs in certain situations.
                    371: <br>
                    372: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/026_ospfd_lsa.patch.sig">
                    373: A source code patch exists which remedies this problem.</a>
                    374: <p>
                    375:
1.24      tj        376: <li id="p027_wscons">
                    377: <strong>027: SECURITY FIX: May 13, 2020</strong>
                    378: &nbsp; <i>All architectures</i>
                    379: <br>
                    380: An out-of-bounds index access in wscons(4) can cause a kernel crash.
                    381: <br>
                    382: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/027_wscons.patch.sig">
                    383: A source code patch exists which remedies this problem.</a>
                    384: <p>
                    385:
1.26      tj        386: <li id="p028_unbound">
                    387: <strong>028: SECURITY FIX: May 22, 2020</strong>
1.25      tj        388: &nbsp; <i>All architectures</i>
                    389: <br>
                    390: Specially crafted queries may crash unbound and unwind.
                    391: Both can be tricked into amplifying an incoming query.
                    392: <br>
1.26      tj        393: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/028_unbound.patch.sig">
1.25      tj        394: A source code patch exists which remedies this problem.</a>
                    395: <p>
                    396:
1.27      tj        397: <li id="p029_perl">
                    398: <strong>029: SECURITY FIX: June 1, 2020</strong>
                    399: &nbsp; <i>All architectures</i>
                    400: <br>
                    401: Several problems in Perl's regular expression compiler could lead to
                    402: corruption of the intermediate language state of a compiled regular
                    403: expression.
                    404: <br>
                    405: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/029_perl.patch.sig">
                    406: A source code patch exists which remedies this problem.</a>
                    407: <p>
                    408:
1.28      tj        409: <li id="p030_hid">
                    410: <strong>030: SECURITY FIX: June 5, 2020</strong>
                    411: &nbsp; <i>All architectures</i>
                    412: <br>
                    413: Malicious HID descriptors could be misparsed.
                    414: <br>
                    415: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/030_hid.patch.sig">
                    416: A source code patch exists which remedies this problem.</a>
                    417: <p>
                    418:
1.29      tj        419: <li id="p031_asr">
                    420: <strong>031: RELIABILITY FIX: June 8, 2020</strong>
                    421: &nbsp; <i>All architectures</i>
                    422: <br>
                    423: libc's resolver could get into a corrupted state.
                    424: <br>
                    425: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/031_asr.patch.sig">
                    426: A source code patch exists which remedies this problem.</a>
                    427: <p>
                    428:
1.30      tj        429: <li id="p032_x509">
                    430: <strong>032: RELIABILITY FIX: June 11, 2020</strong>
                    431: &nbsp; <i>All architectures</i>
                    432: <br>
                    433: libcrypto may fail to build a valid certificate chain due to
                    434: expired untrusted issuer certificates.
                    435: <br>
                    436: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/032_x509.patch.sig">
                    437: A source code patch exists which remedies this problem.</a>
                    438: <p>
                    439:
1.31      tj        440: <li id="p033_shmget">
                    441: <strong>033: SECURITY FIX: July 9, 2020</strong>
                    442: &nbsp; <i>All architectures</i>
                    443: <br>
                    444: shmget IPC_STAT leaked some kernel data.
                    445: <br>
                    446: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/033_shmget.patch.sig">
                    447: A source code patch exists which remedies this problem.</a>
                    448: <p>
                    449:
1.32      tj        450: <li id="p034_tty">
                    451: <strong>034: RELIABILITY FIX: July 16, 2020</strong>
                    452: &nbsp; <i>All architectures</i>
                    453: <br>
                    454: tty subsystem abuse can impact performance badly.
                    455: <br>
                    456: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/034_tty.patch.sig">
                    457: A source code patch exists which remedies this problem.</a>
                    458: <p>
                    459:
1.33      tj        460: <li id="p035_tty">
                    461: <strong>035: RELIABILITY FIX: July 22, 2020</strong>
                    462: &nbsp; <i>All architectures</i>
                    463: <br>
                    464: Only pty devices need reprint delays.
                    465: <br>
                    466: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/035_tty.patch.sig">
                    467: A source code patch exists which remedies this problem.</a>
                    468: <p>
                    469:
1.34      bluhm     470: <li id="p036_iked">
                    471: <strong>036: SECURITY FIX: July 27, 2020</strong>
                    472: &nbsp; <i>All architectures</i>
                    473: <br>
                    474: In iked, incorrect use of EVP_PKEY_cmp allows an authentication bypass.
                    475: <br>
                    476: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/036_iked.patch.sig">
                    477: A source code patch exists which remedies this problem.</a>
                    478: <p>
                    479:
1.35      tj        480: <li id="p037_ximcp">
                    481: <strong>037: SECURITY FIX: July 31, 2020</strong>
                    482: &nbsp; <i>All architectures</i>
                    483: <br>
                    484: Malformed messages can cause heap corruption in the X Input Method
                    485: client implementation in libX11.
                    486: <br>
                    487: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/037_ximcp.patch.sig">
                    488: A source code patch exists which remedies this problem.</a>
                    489: <p>
                    490:
                    491: <li id="p038_dix">
                    492: <strong>038: SECURITY FIX: July 31, 2020</strong>
                    493: &nbsp; <i>All architectures</i>
                    494: <br>
                    495: Pixmaps inside the xserver were an info leak.
                    496: <br>
                    497: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/038_dix.patch.sig">
                    498: A source code patch exists which remedies this problem.</a>
                    499: <p>
                    500:
1.36      tj        501: <li id="p039_ximcp">
                    502: <strong>039: RELIABILITY FIX: August 7, 2020</strong>
                    503: &nbsp; <i>All architectures</i>
                    504: <br>
                    505: The recent security errata 037 broke X11 input methods.
                    506: <br>
                    507: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/039_ximcp.patch.sig">
                    508: A source code patch exists which remedies this problem.</a>
                    509: <p>
                    510:
1.37      tj        511: <li id="p040_xinitom">
                    512: <strong>040: SECURITY FIX: August 25, 2020</strong>
                    513: &nbsp; <i>All architectures</i>
                    514: <br>
                    515: An integer overflow in libX11 could lead to a double free.
                    516: Additionally fix a regression in ximcp.
                    517: <br>
                    518: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/040_xinitom.patch.sig">
                    519: A source code patch exists which remedies this problem.</a>
                    520: <p>
                    521:
                    522: <li id="p041_xserverlen">
                    523: <strong>041: SECURITY FIX: August 25, 2020</strong>
                    524: &nbsp; <i>All architectures</i>
                    525: <br>
                    526: Various X server extensions had deficient input validation.
                    527: <br>
                    528: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/041_xserverlen.patch.sig">
                    529: A source code patch exists which remedies this problem.</a>
                    530: <p>
                    531:
1.38      tj        532: <li id="p042_amdgpu">
                    533: <strong>042: SECURITY FIX: September 5, 2020</strong>
                    534: &nbsp; <i>amd64, arm64</i>
                    535: <br>
                    536: A buffer overflow was discovered in an amdgpu ioctl.
                    537: <br>
                    538: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/042_amdgpu.patch.sig">
                    539: A source code patch exists which remedies this problem.</a>
                    540: <p>
                    541:
1.1       deraadt   542: </ul>
                    543:
1.17      tj        544: <hr>