Hot Fix Downloads for Linux for x64
General Information about Hot Fixes
L8X001 was replaced by L8X038 |
L8X002 was replaced by L8X049 |
L8X003 was replaced by L8X038 |
L8X004 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
69864 | The FILENAME statement in Base SAS® contains a stack smashing vulnerability | L8X004 | |||||
|
Top ^ |
L8X005 was replaced by L8X038 |
L8X006 was replaced by L8X067 |
L8X007 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
69920 | Attempting to clone a Git repository fails with "ERROR: Unable to load libgit2.module" | L8X007 | |||||
69932 | Attempting to clone a Git repository with the ed25519 keygen algorithm fails with "ERROR: Failed to authenticate with the remote repo" | L8X007 | |||||
|
Top ^ |
L8X008 was replaced by L8X067 |
L8X009 was replaced by L8X034 |
L8X010 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
69963 | The FCOPY function fails with a "Segmentation Violation" error when you copy a file using the WebDAV access method to an alfresco server | L8X010 | |||||
|
Top ^ |
L8X011 was replaced by L8X038 |
L8X012 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
69951 | The message "ERROR: Unexpected error detected in function HASHING_FILE" can occur when the second argument to the function refers to an empty file | L8X012 | |||||
NOTE: If you install this hot fix, you must also install hot fix M2A001 for SAS Threaded Kernel User Functions 9.4_M8. | |||||||
|
Top ^ |
L8X013 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70068 | SAS® Deployment Tester is unable to read data from SAS® Operational Qualification Tool | L8X013 | |||||
|
Top ^ |
L8X014 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70087 | Trying to access a BigQuery table or MongoDB document might result in an "UNABLE TO ACCESS MESSAGE" error | L8X014 | |||||
|
Top ^ |
L8X015 was replaced by L8X040 |
L8X016 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70048 | CALL IS8601_CONVERT does not compute durations properly | L8X016 | |||||
|
Top ^ |
L8X017 was replaced by L8X022 |
L8X018 was replaced by L8X020 |
L8X019 was replaced by L8X061 |
L8X020 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70092 | The ZIPSTATE function returns an "Invalid argument" message when passing in military ZIP codes | L8X018 | |||||
|
Top ^ |
L8X021 was replaced by L8X040 |
L8X022 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70100 | Using the SORT procedure with the OVERWRITE option might result in an unsorted table | L8X017 | |||||
70219 | Running PROC SORT on a DB2 table with OUT= produces fewer rows than expected | L8X022 | |||||
|
Top ^ |
L8X024 was replaced by L8X067 |
L8X025 was replaced by L8X061 |
L8X026 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70337 | The KSUBSTRN function might remove trailing blanks after you upgrade to SAS® 9.4M7 (TS1M7) or later | L8X026 | |||||
|
Top ^ |
L8X027 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70357 | The SGPANEL procedure causes SAS® software to terminate | L8X027 | |||||
|
Top ^ |
L8X030 was replaced by L8X067 |
L8X031 was replaced by L8X040 |
L8X032 was replaced by L8X049 |
L8X033 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70487 | Code run with the SAS® In-Database Code Accelerator for Hadoop on a SAS® Workspace Server might return an error when writing to a local XML file | L8X033 | |||||
|
Top ^ |
L8X034 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
69972 | Using SAS/ACCESS® Interface to ODBC together with a SAP HANA ODBC driver might cause an insufficient memory error | L8X009 | |||||
NOTE: If you install this hot fix, you must also install hot fix M3G004 for SAS/ACCESS Interface to ODBC 9.4_M8. If you install this hot fix, you must also install hot fix M5Z003 for SAS/ACCESS Interface to DB2 9.45. If you install this hot fix, you must also install hot fix M5F003 for SAS/ACCESS Interface to Microsoft SQL Server 9.46. | |||||||
|
Top ^ |
L8X035 was replaced by L8X067 |
L8X037 was replaced by L8X053 |
L8X038 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
69854 | SAS® 9.4M8 (TS1M8) installations fail on Microsoft Windows 11, and Windows Server 2022 Datacenter and Standard; and starting SAS® produces an error | L8X001 | |||||
69871 | MXG code cannot read TYPE 70/72 records that are longer than 32K record due to a change that IBM made | L8X005 | |||||
69974 | Base SAS® does not correctly detect a Linux distribution on start-up and returns an "Unrecognized Linux Distribution" note | L8X011 | |||||
70340 | The creation of very large log files in SAS® Studio could cause excessive and retained heap usage on SASServer2_1 | L8X038 | |||||
NOTE: If you install this hot fix, you must also install hot fix L8Y001 for SAS Threaded Kernel Core Routines 9.4_M8. If you install this hot fix to address the issue described in SAS Note 70340, you must also apply Base SAS 9.4_M8 hot fixes L8X067, and L8X053. | |||||||
|
Top ^ |
L8X040 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70049 | A floating point exception error occurs when using PROC METALIB | L8X015 | |||||
70582 | A Read access violation or segmentation violation occurs when registering DB2 Tables with foreign keys in the SAS® metadata | L8X040 | |||||
|
Top ^ |
L8X042 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70621 | Using %SYSCALL causes a Read Access Violation error | L8X042 | |||||
|
Top ^ |
L8X043 was replaced by L8X049 |
L8X044 was replaced by L8X061 |
L8X045 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70709 | A memory corruption vulnerability exists in Base SAS® and SAS/STAT® | L8X045 | |||||
NOTE: All Operating Systems: To ensure that you apply all the relevant hot fixes for this product and release, search for 70709. Then, download and apply the hot fixes listed on the page for SAS Note 70709. To ensure that your system is completely up to date with all fixes, consider using the SAS Hot Fix Analysis, Download and Deployment Tool (SASHFADD). | |||||||
|
Top ^ |
L8X046 was replaced by L8X067 |
L8X047 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70709 | A memory corruption vulnerability exists in Base SAS® and SAS/STAT® | L8X047 | |||||
NOTE: If you install this hot fix you must also apply L8X067 for Base SAS 9.4_M8 and N3S001 for Base SAS User Interface 9.4 - M8 All Operating Systems: To ensure that you apply all the relevant hot fixes for this product and release, search for 70709. Then, download and apply the hot fixes listed on the page for SAS Note 70709. To ensure that your system is completely up to date with all fixes, consider using the SAS Hot Fix Analysis, Download and Deployment Tool (SASHFADD). | |||||||
|
Top ^ |
L8X048 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70722 | Running PROC UPLOAD or PROC DOWNLOAD between a SAS/CONNECT® client on SAS® Viya® and a SAS® 9.4 SAS/CONNECT® spawner fails with "Insufficient memory" | L8X048 | |||||
|
Top ^ |
L8X049 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70088 | Passwords appear in the SAS® log when the SQL procedure contains the _tree option and an embedded LIBNAME statement | L8X002 | |||||
70090 | A "Parse Failure..." message occurs in the SAS® log when running SPD Server PROC SQL with hex literals | L8X002 | |||||
70279 | The SUBSTRN and KSUBSTRN functions used in PROC SQL with a numeric first argument return an incorrect result | L8X032 | |||||
70641 | The column alias is not used in an ON clause that is sent to a database in SAS/ACCESS® Interface to Vertica | L8X043 | |||||
70801 | The SQL procedure displays the note “The execution of this query involves performing one or more Cartesian product joins that can not be optimized” | L8X049 | |||||
|
Top ^ |
L8X050 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70709 | A memory corruption vulnerability exists in Base SAS® and SAS/STAT® | L8X050 | |||||
NOTE: All Operating Systems: To ensure that you apply all the relevant hot fixes for this product and release, search for 70709. Then, download and apply the hot fixes listed on the page for SAS Note 70709. To ensure that your system is completely up to date with all fixes, consider using the SAS Hot Fix Analysis, Download and Deployment Tool (SASHFADD). | |||||||
|
Top ^ |
L8X051 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70776 | PROC HPFEVENTS might result in a Read Access Violation or Segmentation Violation | L8X051 | |||||
70778 | PROC TIMEID might result in a Floating Point Exception or Segmentation Violation | L8X051 | |||||
NOTE: If you install this hot fix and have SAS/ETS 15.3 installed, you must also install hot fix N4M001. | |||||||
|
Top ^ |
L8X052 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70714 | A potential memory leak occurs in SAS® 9.4M8 (TS1M8) with the “ERROR: Read Access Violation DATASTEP” | L8X052 | |||||
|
Top ^ |
L8X053 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70340 | The creation of very large log files in SAS® Studio could cause excessive and retained heap usage on SASServer2_1 | L8X037 | |||||
70797 | Running SAS ® 9.4M7 (TS1M7) or SAS® 9.4M8 (TS1M8) with non-English European languages might result in an error | L8X053 | |||||
NOTE: If you install this hot fix to address the issue described in SAS Note 70340, you must also apply Base SAS 9.4_M8 hot fixes L8X067, L8X038 (Unix and Windows only), L8X068(MVS only) | |||||||
|
Top ^ |
L8X056 was replaced by L8X061 |
L8X057 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70709 | A memory corruption vulnerability exists in Base SAS® and SAS/STAT® | L8X057 | |||||
|
Top ^ |
L8X058 was replaced by L8X061 |
L8X060 was replaced by L8X067 |
L8X061 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70140 | The ODS PDF destination with ACCESSIBLE option and the PROC FACTOR procedure might generate a segmentation violation error | L8X019 | |||||
70305 | Using the PDFSECURITY=HIGH system option results in PDF output that is encoded with 128-bit RC4 encoding instead of AES 256 encoding | L8X025 | |||||
70709 | A memory corruption vulnerability exists in Base SAS® and SAS/STAT® | L8X044 | |||||
70805 | Some data points are plotted incorrectly in ODS Graphics output if there is a break in the Y axis | L8X056 | |||||
70827 | Text might be truncated when using the Column_Span option in the ODS Region statement | L8X058 | |||||
70831 | Using PROC MIXED with the ODS PDF destination, ENCODING=WHEBREW, and LOCALE=HEBREW_ISRAEL causes SAS® software to terminate | L8X061 | |||||
NOTE: All Operating Systems: To ensure that you apply all the relevant hot fixes for this product and release, search for 70709. Then, download and apply the hot fixes listed on the page for SAS Note 70709. To ensure that your system is completely up to date with all fixes, consider using the SAS Hot Fix Analysis, Download and Deployment Tool (SASHFADD). | |||||||
|
Top ^ |
L8X062 was replaced by L8X067 |
L8X064 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70709 | A memory corruption vulnerability exists in Base SAS® and SAS/STAT® | L8X064 | |||||
NOTE: All Operating Systems: To ensure that you apply all the relevant hot fixes for this product and release, search for 70709. Then, download and apply the hot fixes listed on the page for SAS Note 70709. To ensure that your system is completely up to date with all fixes, consider using the SAS Hot Fix Analysis, Download and Deployment Tool (SASHFADD). | |||||||
|
Top ^ |
L8X065 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70709 | A memory corruption vulnerability exists in Base SAS® and SAS/STAT® | L8X065 | |||||
NOTE: All Operating Systems: To ensure that you apply all the relevant hot fixes for this product and release, search for 70709. Then, download and apply the hot fixes listed on the page for SAS Note 70709. To ensure that your system is completely up to date with all fixes, consider using the SAS Hot Fix Analysis, Download and Deployment Tool (SASHFADD). | |||||||
|
Top ^ |
L8X066 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70709 | A memory corruption vulnerability exists in Base SAS® and SAS/STAT® | L8X066 | |||||
NOTE: All Operating Systems: To ensure that you apply all the relevant hot fixes for this product and release, search for 70709. Then, download and apply the hot fixes listed on the page for SAS Note 70709. To ensure that your system is completely up to date with all fixes, consider using the SAS Hot Fix Analysis, Download and Deployment Tool (SASHFADD). | |||||||
|
Top ^ |
L8X067 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
69952 | Using the * comment operator mid-line within a format definition in PROC FORMAT might cause subsequent procedures steps to abend | L8X006 | |||||
69899 | Calling a user-defined function with the PROC FORMAT OTHER= argument can cause SAS® to stop responding | L8X008 | |||||
70340 | The creation of very large log files in SAS® Studio could cause excessive and retained heap usage on SASServer2_1 | L8X035 | |||||
70431 | The UNIVARIATE procedure might generate a Segmentation Violation Error in SAS | L8X035 | |||||
70709 | A memory corruption vulnerability exists in Base SAS® and SAS/STAT® | L8X046 | |||||
70869 | A security vulnerability exists when IOM TRACE logging is enabled | L8X060 | |||||
NOTE: If you install this hot fix to address the issue described in SAS Note 70402, you must also apply L8X068 and M4B009 for Base SAS 9.4_M8. If you install this hot fix to address the issue described in SAS Note 70340, you must also apply Base SAS 9.4_M8 hot fixes L8X053, L8X038 (Unix and Windows only), L8X068(MVS only) If you install this hot fix you must also apply L8X047 for Base SAS 9.4_M8 and N3S001 for Base SAS User Interface 9.4 - M8 If you install this hot fix to address the issue described in SAS Note 70869, you must also apply M4B009 for Base SAS 9.4_M8. All Operating Systems: To ensure that you apply all the relevant hot fixes for this product and release, search for 70709. Then, download and apply the hot fixes listed on the page for SAS Note 70709. To ensure that your system is completely up to date with all fixes, consider using the SAS Hot Fix Analysis, Download and Deployment Tool (SASHFADD). | |||||||
|
Top ^ |
M4B001 was replaced by M4B009 |
M4B002 was replaced by M4B009 |
M4B004 was replaced by M4B009 |
M4B005 was replaced by M4B009 |
M4B006 was replaced by M4B009 |
M4B007 was replaced by M4B009 |
M4B008 was replaced by M4B009 |
M4B009 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70230 | SAS® 9.4M8 (TS1M8) might display an OpenSSL 3 "legacy" provider warning at initialization | M4B001 | |||||
70859 | An intermittent exception occurs in SAS Workspace Server when a client is no longer running | M4B002 | |||||
70496 | The SAS® Environment Manager Service Architecture enablement might fail on getDBMirror if FIPS is enabled | M4B004 | |||||
70783 | SAS® Infrastructure for Risk Management job flows might fail due to an encryption failure | M4B005 | |||||
70869 | A security vulnerability exists when IOM TRACE logging is enabled | M4B006 | |||||
70846 | SAS® 9.4M8 (TS1M8) client connections to SAS® Cloud Analytic Services fail with the error "Missing CA trust list" | M4B007 | |||||
70905 | Support for the 2048 and 4096 key lengths with AES encryption on z/OS | M4B008 | |||||
70504 | Support for the IBM "System SSL" for z64 | M4B009 | |||||
NOTE: If you install this hot fix to address the issue described in SAS Note 70402, you must also apply L8X068 and L8X067 for Base SAS 9.4_M8. If you install this hot fix to address the issue described in SAS Note 70869, you must also apply L8X067 for Base SAS 9.4_M8. | |||||||
| |||||||
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
Top ^ |
M8S001 was replaced by M8S002 |
M8S002 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70344 | The PHREG procedure contains a stack-corruption vulnerability if you incorrectly specify the RUN statement | M8S001 | |||||
70505 | PROC FCMP package names might not find the function and return "WARNING: Cannot find function 'function_name' in any of the libraries specified" | M8S001 | |||||
70466 | SAS® Model Implementation Platform returns an error when loading a large number of models | M8S001 | |||||
70709 | A memory corruption vulnerability exists in Base SAS® and SAS/STAT® | M8S002 | |||||
NOTE: All Operating Systems: To ensure that you apply all the relevant hot fixes for this product and release, search for 70709. Then, download and apply the hot fixes listed on the page for SAS Note 70709. To ensure that your system is completely up to date with all fixes, consider using the SAS Hot Fix Analysis, Download and Deployment Tool (SASHFADD). | |||||||
| |||||||
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
Top ^ |
N4Z001 for Linux for x64 | |||||||
Base SAS 9.4_M8 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
70804 | The message "SSL Error: Invalid subject name in partner's certificate..." can occur when accessing Amazon Web Services (AWS) S3 | N4Z001 | |||||
69457 | A "Parse failed" error appears when you use PROC S3 and CAS actions to access S3 sources using either custom regions or predefined regions | N4Z001 | |||||
|
Top ^ |
PLEASE CAREFULLY READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT ("AGREEMENT") BEFORE DOWNLOADING MATERIALS FROM THIS SITE. BY DOWNLOADING ANY MATERIALS FROM THIS SITE, YOU ARE AGREEING TO THESE TERMS.
|
You are downloading software code ("Code") which will become part of a product ("Software") you currently have licensed from SAS Institute Inc. or one of its subsidiaries ("the Institute"). this Code is designed to either correct an error in the Software
or to add functionality to the Software. The code is governed by the same agreement which governs the Software. If you do not have an existing agreement with the Institute governing the Software, you may not download the Code.
|
SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. Other brand and product names are registered
trademarks or trademarks of their respective companies.
|
Copyright © SAS Institute Inc. All Rights Reserved.
|