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

Annotation of www/errata61.html, Revision 1.47

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