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

Annotation of www/errata61.html, Revision 1.51

1.39      bentley     1: <!doctype html>
                      2: <html lang=en id=errata>
                      3: <meta charset=utf-8>
                      4:
1.1       tj          5: <title>OpenBSD 6.1 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/errata61.html">
                     10:
                     11: <!--
                     12:                        IMPORTANT REMINDER
                     13:        IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
                     14: -->
                     15:
1.39      bentley    16: <h2 id=OpenBSD>
1.1       tj         17: <a href="index.html">
1.39      bentley    18: <i>Open</i><b>BSD</b></a>
                     19: 6.1 Errata
1.1       tj         20: </h2>
                     21: <hr>
                     22:
                     23: For errata on a certain release, click below:<br>
1.41      schwarze   24: <a href="errata20.html">2.0</a>,
1.1       tj         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.41      schwarze   40: <br>
1.1       tj         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.41      schwarze   57: <br>
1.1       tj         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>,
1.23      deraadt    66: <a href="errata60.html">6.0</a>,
1.34      deraadt    67: <a href="errata62.html">6.2</a>,
1.37      deraadt    68: <a href="errata63.html">6.3</a>,
1.38      deraadt    69: <a href="errata64.html">6.4</a>,
1.40      deraadt    70: <a href="errata65.html">6.5</a>,
1.42      deraadt    71: <a href="errata66.html">6.6</a>,
1.43      deraadt    72: <a href="errata67.html">6.7</a>,
1.44      deraadt    73: <a href="errata68.html">6.8</a>,
1.45      tj         74: <br>
1.46      deraadt    75: <a href="errata69.html">6.9</a>,
1.47      deraadt    76: <a href="errata70.html">7.0</a>,
1.48      deraadt    77: <a href="errata71.html">7.1</a>,
1.49      tj         78: <a href="errata72.html">7.2</a>,
1.50      tj         79: <a href="errata73.html">7.3</a>,
1.51    ! tj         80: <a href="errata74.html">7.4</a>,
        !            81: <a href="errata75.html">7.5</a>.
1.1       tj         82: <hr>
                     83:
                     84: <p>
                     85: Patches for the OpenBSD base system are distributed as unified diffs.
                     86: Each patch is cryptographically signed with the
1.15      tb         87: <a href="https://man.openbsd.org/OpenBSD-6.1/signify.1">signify(1)</a> tool and contains
1.1       tj         88: usage instructions.
                     89: All the following patches are also available in one
                     90: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1.tar.gz">tar.gz file</a>
                     91: for convenience.
                     92:
                     93: <p>
1.32      tj         94: Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
                     95: utility can be used to apply binary updates on the following architectures:
1.35      tj         96: amd64, i386.
1.32      tj         97:
                     98: <p>
1.1       tj         99: Patches for supported releases are also incorporated into the
1.35      tj        100: <a href="stable.html">-stable branch</a>.
1.1       tj        101:
                    102: <hr>
                    103:
                    104: <ul>
                    105:
1.4       tj        106: <li id="p001_dhcpd">
1.39      bentley   107: <strong>001: INTEROPERABILITY FIX: May 2, 2017</strong>
1.4       tj        108: &nbsp; <i>All architectures</i>
                    109: <br>
                    110: dhcpd unconditionally echoed the client identifier, preventing some devices
1.5       tb        111: from acquiring a lease.
1.4       tj        112: <br>
                    113: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/001_dhcpd.patch.sig">
                    114: A source code patch exists which remedies this problem.</a>
                    115: <p>
                    116:
                    117: <li id="p002_vmmfpu">
1.39      bentley   118: <strong>002: SECURITY FIX: May 2, 2017</strong>
1.6       mlarkin   119: &nbsp; <i>amd64</i>
1.4       tj        120: <br>
                    121: vmm mismanaged floating point contexts.
                    122: <br>
                    123: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/002_vmmfpu.patch.sig">
                    124: A source code patch exists which remedies this problem.</a>
                    125: <p>
                    126:
                    127: <li id="p003_libressl">
1.39      bentley   128: <strong>003: SECURITY FIX: May 2, 2017</strong>
1.4       tj        129: &nbsp; <i>All architectures</i>
                    130: <br>
                    131: A consistency check error could cause programs to incorrectly verify
                    132: TLS certificates when using callbacks that always return 1.
                    133: <br>
                    134: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/003_libressl.patch.sig">
                    135: A source code patch exists which remedies this problem.</a>
                    136: <p>
                    137:
                    138: <li id="p004_softraid_concat">
1.39      bentley   139: <strong>004: RELIABILITY FIX: May 2, 2017</strong>
1.4       tj        140: &nbsp; <i>All architectures</i>
                    141: <br>
                    142: softraid was unable to create usable concat volumes because
                    143: it always set the size of the volume to zero sectors.
                    144: <br>
                    145: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/004_softraid_concat.patch.sig">
                    146: A source code patch exists which remedies this problem.</a>
                    147: <p>
1.1       tj        148:
1.7       tj        149: <li id="p005_pf_src_tracking">
1.39      bentley   150: <strong>005: RELIABILITY FIX: May 6, 2017</strong>
1.7       tj        151: &nbsp; <i>All architectures</i>
                    152: <br>
                    153: Expired pf source tracking entries never got removed, leading to
                    154: memory exhaustion.
                    155: <br>
                    156: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/005_pf_src_tracking.patch.sig">
                    157: A source code patch exists which remedies this problem.</a>
                    158: <p>
                    159:
1.8       tj        160: <li id="p006_libssl">
1.39      bentley   161: <strong>006: RELIABILITY FIX: May 8, 2017</strong>
1.8       tj        162: &nbsp; <i>All architectures</i>
                    163: <br>
                    164: Incorrect DTLS cookie handling can result in a NULL pointer dereference.
                    165: <br>
                    166: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/006_libssl.patch.sig">
                    167: A source code patch exists which remedies this problem.</a>
                    168: <p>
                    169:
1.9       tj        170: <li id="p007_freetype">
1.39      bentley   171: <strong>007: SECURITY FIX: May 13, 2017</strong>
1.9       tj        172: &nbsp; <i>All architectures</i>
                    173: <br>
                    174: Heap-based buffer overflows in freetype can result in out-of-bounds writes.
                    175: <br>
                    176: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/007_freetype.patch.sig">
                    177: A source code patch exists which remedies this problem.</a>
                    178: <p>
                    179:
1.11      tj        180: <li id="p008_exec_subr">
1.39      bentley   181: <strong>008: SECURITY FIX: May 19, 2017</strong>
1.11      tj        182: &nbsp; <i>All architectures</i>
                    183: <br>
                    184: An additional mitigation is added by placing a gap of 1 MB between the
                    185: stack and mmap spaces.
                    186: <br>
                    187: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/008_exec_subr.patch.sig">
                    188: A source code patch exists which remedies this problem.</a>
                    189: <p>
                    190:
1.12      tj        191: <li id="p009_icmp_opts">
1.39      bentley   192: <strong>009: RELIABILITY FIX: May 22, 2017</strong>
1.12      tj        193: &nbsp; <i>All architectures</i>
                    194: <br>
1.14      tj        195: The kernel could leak memory when processing ICMP packets with IP options.
1.12      tj        196: Note that pf blocks such packets by default.
                    197: <br>
                    198: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/009_icmp_opts.patch.sig">
                    199: A source code patch exists which remedies this problem.</a>
                    200: <p>
                    201:
1.13      tj        202: <li id="p010_perl">
1.39      bentley   203: <strong>010: SECURITY FIX: June 4, 2017</strong>
1.13      tj        204: &nbsp; <i>All architectures</i>
                    205: <br>
                    206: A race condition exists in the File::Path perl module.
                    207: <br>
                    208: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/010_perl.patch.sig">
1.14      tj        209: A source code patch exists which remedies this problem.</a>
                    210: <p>
                    211:
                    212: <li id="p011_sti">
1.39      bentley   213: <strong>011: SECURITY FIX: June 12, 2017</strong>
1.14      tj        214: &nbsp; <i>hppa</i>
                    215: <br>
                    216: An integer overflow exists in two range checks of the sti(4) display driver.
                    217: <br>
                    218: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/011_sti.patch.sig">
                    219: A source code patch exists which remedies this problem.</a>
                    220: <p>
                    221:
                    222: <li id="p012_wsmux">
1.39      bentley   223: <strong>012: RELIABILITY FIX: June 12, 2017</strong>
1.14      tj        224: &nbsp; <i>All architectures</i>
                    225: <br>
                    226: An unprivileged user can cause a kernel crash.
                    227: <br>
                    228: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/012_wsmux.patch.sig">
1.13      tj        229: A source code patch exists which remedies this problem.</a>
                    230: <p>
                    231:
1.16      tj        232: <li id="p013_icmp6_linklocal">
1.39      bentley   233: <strong>013: RELIABILITY FIX: June 27, 2017</strong>
1.16      tj        234: &nbsp; <i>All architectures</i>
                    235: <br>
                    236: When pinging an IPv6 link-local address, the reflected packet had
                    237: ::1 as source address.  The echo reply was ignored as it must be
                    238: from the link-local address.
                    239: <br>
                    240: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/013_icmp6_linklocal.patch.sig">
                    241: A source code patch exists which remedies this problem.</a>
                    242: <p>
                    243:
1.17      tj        244: <li id="p014_libcrypto">
1.39      bentley   245: <strong>014: RELIABILITY FIX: July 5, 2017</strong>
1.17      tj        246: &nbsp; <i>All architectures</i>
                    247: <br>
                    248: Self-issued certificates are improperly treated as self-signed certificates,
                    249: leading to possible verification failures.
                    250: <br>
                    251: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/014_libcrypto.patch.sig">
                    252: A source code patch exists which remedies this problem.</a>
                    253: <p>
                    254:
1.18      tj        255: <li id="p015_sigio">
1.39      bentley   256: <strong>015: RELIABILITY FIX: August 3, 2017</strong>
1.18      tj        257: &nbsp; <i>All architectures</i>
                    258: <br>
                    259: A SIGIO-related use-after-free can occur in two drivers.
                    260: <br>
                    261: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/015_sigio.patch.sig">
                    262: A source code patch exists which remedies this problem.</a>
                    263: <p>
                    264:
                    265: <li id="p016_sendsyslog">
1.39      bentley   266: <strong>016: RELIABILITY FIX: August 3, 2017</strong>
1.18      tj        267: &nbsp; <i>All architectures</i>
                    268: <br>
                    269: A missing length check in sendsyslog() may result in a kernel panic.
                    270: <br>
                    271: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/016_sendsyslog.patch.sig">
                    272: A source code patch exists which remedies this problem.</a>
                    273: <p>
                    274:
                    275: <li id="p017_fuse">
1.39      bentley   276: <strong>017: SECURITY FIX: August 3, 2017</strong>
1.18      tj        277: &nbsp; <i>All architectures</i>
                    278: <br>
                    279: An out-of-bound read in vfs_getcwd_scandir() (mainly used for FUSE)
                    280: may result in a kernel panic or info leak.
                    281: <br>
                    282: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/017_fuse.patch.sig">
                    283: A source code patch exists which remedies this problem.</a>
                    284: <p>
                    285:
                    286: <li id="p018_recv">
1.39      bentley   287: <strong>018: SECURITY FIX: August 3, 2017</strong>
1.18      tj        288: &nbsp; <i>All architectures</i>
                    289: <br>
                    290: An alignment issue in recv() may result in an info leak via ktrace().
                    291: <br>
                    292: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/018_recv.patch.sig">
                    293: A source code patch exists which remedies this problem.</a>
                    294: <p>
                    295:
                    296: <li id="p019_tcp_usrreq">
1.39      bentley   297: <strong>019: SECURITY FIX: August 3, 2017</strong>
1.18      tj        298: &nbsp; <i>All architectures</i>
                    299: <br>
                    300: With an invalid address family, tcp_usrreq() may take an unintended code path.
                    301: <br>
                    302: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/019_tcp_usrreq.patch.sig">
                    303: A source code patch exists which remedies this problem.</a>
                    304: <p>
                    305:
                    306: <li id="p020_sockaddr">
1.39      bentley   307: <strong>020: SECURITY FIX: August 3, 2017</strong>
1.18      tj        308: &nbsp; <i>All architectures</i>
                    309: <br>
                    310: Missing socket address validation from userland may result in an info leak.
                    311: <br>
                    312: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/020_sockaddr.patch.sig">
                    313: A source code patch exists which remedies this problem.</a>
                    314: <p>
                    315:
                    316: <li id="p021_ptrace">
1.39      bentley   317: <strong>021: SECURITY FIX: August 3, 2017</strong>
1.18      tj        318: &nbsp; <i>All architectures</i>
                    319: <br>
                    320: An uninitialized variable in ptrace() may result in an info leak.
                    321: <br>
                    322: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/021_ptrace.patch.sig">
                    323: A source code patch exists which remedies this problem.</a>
                    324: <p>
                    325:
                    326: <li id="p022_fcntl">
1.39      bentley   327: <strong>022: SECURITY FIX: August 3, 2017</strong>
1.18      tj        328: &nbsp; <i>All architectures</i>
                    329: <br>
                    330: An uninitialized variable in fcntl() may result in an info leak.
                    331: <br>
                    332: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/022_fcntl.patch.sig">
                    333: A source code patch exists which remedies this problem.</a>
                    334: <p>
                    335:
                    336: <li id="p023_wsdisplay">
1.39      bentley   337: <strong>023: RELIABILITY FIX: August 3, 2017</strong>
1.18      tj        338: &nbsp; <i>All architectures</i>
                    339: <br>
                    340: An integer overflow in wsdisplay_cfg_ioctl() may result in an out-of-bounds
                    341: read.
                    342: <br>
                    343: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/023_wsdisplay.patch.sig">
                    344: A source code patch exists which remedies this problem.</a>
                    345: <p>
                    346:
                    347: <li id="p024_sosplice">
1.39      bentley   348: <strong>024: SECURITY FIX: August 3, 2017</strong>
1.18      tj        349: &nbsp; <i>All architectures</i>
                    350: <br>
                    351: A race condition in sosplice() may result in a kernel memory leak.
                    352: <br>
                    353: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/024_sosplice.patch.sig">
                    354: A source code patch exists which remedies this problem.</a>
                    355: <p>
                    356:
                    357: <li id="p025_ieee80211">
1.39      bentley   358: <strong>025: SECURITY FIX: August 3, 2017</strong>
1.18      tj        359: &nbsp; <i>All architectures</i>
                    360: <br>
                    361: An out of bounds read could occur during processing of EAPOL frames in
                    362: the wireless stack. Information from kernel memory could be leaked to
                    363: root in userland via an ieee80211(9) ioctl.
                    364: <br>
                    365: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/025_ieee80211.patch.sig">
                    366: A source code patch exists which remedies this problem.</a>
                    367: <p>
                    368:
1.19      tj        369: <li id="p026_smap">
1.39      bentley   370: <strong>026: SECURITY FIX: August 26, 2017</strong>
1.19      tj        371: &nbsp; <i>amd64 and i386</i>
                    372: <br>
                    373: SMAP enforcement could be bypassed by userland code.
                    374: <br>
                    375: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/026_smap.patch.sig">
                    376: A source code patch exists which remedies this problem.</a>
                    377: <p>
                    378:
1.20      tj        379: <li id="p027_net80211_replay">
1.39      bentley   380: <strong>027: SECURITY FIX: August 30, 2017</strong>
1.20      tj        381: &nbsp; <i>All architectures</i>
                    382: <br>
                    383: State transition errors could cause reinstallation of old WPA keys.
                    384: <br>
                    385: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/027_net80211_replay.patch.sig">
                    386: A source code patch exists which remedies this problem.</a>
                    387: <p>
                    388:
1.21      tj        389: <li id="p028_perl">
1.39      bentley   390: <strong>028: SECURITY FIX: September 22, 2017</strong>
1.21      tj        391: &nbsp; <i>All architectures</i>
                    392: <br>
                    393: A buffer over-read and heap overflow in perl's regexp may result in
                    394: a crash or memory leak.
                    395: <br>
                    396: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/028_perl.patch.sig">
                    397: A source code patch exists which remedies this problem.</a>
                    398: <p>
                    399:
1.22      tj        400: <li id="p029_tcb">
1.39      bentley   401: <strong>029: RELIABILITY FIX: September 27, 2017</strong>
1.22      tj        402: &nbsp; <i>amd64</i>
                    403: <br>
                    404: Out of bounds TCB settings may result in a kernel panic.
                    405: <br>
                    406: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/029_tcb.patch.sig">
                    407: A source code patch exists which remedies this problem.</a>
                    408: <p>
                    409:
1.24      tj        410: <li id="p030_xrstor">
1.39      bentley   411: <strong>030: RELIABILITY FIX: October 4, 2017</strong>
1.24      tj        412: &nbsp; <i>amd64</i>
                    413: <br>
                    414: An unprivileged user can cause a kernel crash.
                    415: <br>
                    416: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/030_xrstor.patch.sig">
                    417: A source code patch exists which remedies this problem.</a>
                    418: <p>
                    419:
1.25      tj        420: <li id="p031_xrstor_resume">
1.39      bentley   421: <strong>031: SECURITY FIX: October 4, 2017</strong>
1.25      tj        422: &nbsp; <i>amd64</i>
                    423: <br>
                    424: A kernel executable address was leaked to userland.
                    425: <br>
1.26      tj        426: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/031_xrstor_resume.patch.sig">
1.25      tj        427: A source code patch exists which remedies this problem.</a>
                    428: <p>
                    429:
1.27      bluhm     430: <li id="p032_tcb_invalid">
1.39      bentley   431: <strong>032: RELIABILITY FIX: October 13, 2017</strong>
1.27      bluhm     432: &nbsp; <i>amd64</i>
                    433: <br>
                    434: A local user could trigger a kernel panic by using an invalid TCB value.
                    435: <br>
                    436: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/032_tcb_invalid.patch.sig">
                    437: A source code patch exists which remedies this problem.</a>
                    438: <p>
                    439:
1.29      tj        440: <li id="p033_mpls">
1.39      bentley   441: <strong>033: RELIABILITY FIX: December 10, 2017</strong>
1.29      tj        442: &nbsp; All architectures
                    443: <br>
                    444: A number of bugs were discovered in the MPLS stack that can be used to
                    445: remotely trigger a kernel panic.
                    446: <br>
                    447: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/033_mpls.patch.sig">
                    448: A source code patch exists which remedies this problem.</a>
                    449: <p>
                    450:
1.30      tj        451: <li id="p034_ahopts">
1.39      bentley   452: <strong>034: RELIABILITY FIX: February 2, 2018</strong>
1.30      tj        453: &nbsp; <i>All architectures</i>
                    454: <br>
                    455: Specially crafted IPsec AH packets with IP options or IPv6 extension
                    456: headers could crash or hang the kernel.
                    457: <br>
                    458: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/034_ahopts.patch.sig">
                    459: A source code patch exists which remedies this problem.</a>
                    460: <p>
                    461:
                    462: <li id="p035_prevhdr">
1.39      bentley   463: <strong>035: RELIABILITY FIX: February 2, 2018</strong>
1.30      tj        464: &nbsp; <i>All architectures</i>
                    465: <br>
                    466: Processing IPv6 fragments could incorrectly access memory of an mbuf
                    467: chain that is not within an mbuf.  This may crash the kernel.
                    468: <br>
                    469: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/035_prevhdr.patch.sig">
                    470: A source code patch exists which remedies this problem.</a>
                    471: <p>
                    472:
                    473: <li id="p036_etherip">
1.39      bentley   474: <strong>036: SECURITY FIX: February 2, 2018</strong>
1.30      tj        475: &nbsp; <i>All architectures</i>
                    476: <br>
                    477: If the EtherIP tunnel protocol was disabled, IPv6 packets were not
                    478: discarded properly.  This causes a double free in the kernel.
                    479: <br>
                    480: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/036_etherip.patch.sig">
                    481: A source code patch exists which remedies this problem.</a>
                    482: <p>
                    483:
1.31      tj        484: <li id="p037_meltdown">
1.39      bentley   485: <strong>037: SECURITY FIX: March 1, 2018</strong>
1.31      tj        486: &nbsp; <i>amd64</i>
                    487: <br>
                    488: Intel CPUs contain a speculative execution flaw called Meltdown which
                    489: allows userspace programs to access kernel memory.
                    490: <br>
                    491: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/037_meltdown.patch.sig">
                    492: A complex workaround solves the problem.</a>
                    493: <p>
                    494:
1.33      tj        495: <li id="p038_ahauth">
1.39      bentley   496: <strong>038: RELIABILITY FIX: March 20, 2018</strong>
1.33      tj        497: &nbsp; <i>All architectures</i>
                    498: <br>
                    499: The IPsec AH header could be longer than the network packet, resulting in
                    500: a kernel crash.
                    501: <br>
                    502: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/038_ahauth.patch.sig">
                    503: A source code patch exists which remedies this problem.</a>
                    504: <p>
                    505:
1.36      afresh1   506: <li id="p039_perl">
1.39      bentley   507: <strong>039: SECURITY FIX: April 14, 2018</strong>
1.36      afresh1   508: &nbsp; <i>All architectures</i>
                    509: <br>
                    510: Heap overflows exist in perl which can lead to segmentation faults,
                    511: crashes, and reading memory past the buffer.
                    512: <br>
                    513: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/039_perl.patch.sig">
                    514: A source code patch exists which remedies this problem.</a>
                    515: <p>
                    516:
1.1       tj        517: </ul>
                    518:
                    519: <hr>