Datasets:
QLWD
/
code_shield

Dataset card Data Studio Files Community
1
text
stringlengths
64
2.99M
CVE编号: CVE-2024-34649 漏洞描述: 在SMR Sep-2024发布版本之前的多任务框架中的新Dex模式下存在不当的访问控制问题，这允许物理攻击者暂时访问未锁定的屏幕。 披露时间: 2024-09-04 CVSS评分: 2.4 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-34645 漏洞描述: 在SMR Sep-2024 Release 1之前的ThemeCenter中，不当的输入验证允许物理攻击者安装特权应用程序。 披露时间: 2024-09-04 CVSS评分: 6.1 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-34648 漏洞描述: 在SMR Sep-2024版本之前的KnoxMiscPolicy中，不当处理权限不足的问题允许本地攻击者访问敏感数据。 披露时间: 2024-09-04 CVSS评分: 5.1 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-34643 漏洞描述: 在更衣室的SMR Sep-2024版本之前的版本中，关键输入相关功能存在不当的访问控制问题，允许本地攻击者访问受保护的数据。触发此漏洞需要用户进行交互。 披露时间: 2024-09-04 CVSS评分: 4.4 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-34646 漏洞描述: DualDarManagerProxy在SMR Sep-2024发布版本之前的访问控制不当允许本地攻击者造成本地永久拒绝服务。 披露时间: 2024-09-04 CVSS评分: 6.6 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-8421 漏洞描述: No description is available for this CVE. 披露时间: 2024-09-04 CVSS评分: 7.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-7012 漏洞描述: An authentication bypass vulnerability has been identified in Foreman when deployed with External Authentication, due to the puppet-foreman configuration. This issue arises from Apache's mod_proxy not properly unsetting headers because of restrictions on underscores in HTTP headers, allowing authentication through a malformed header. This flaw impacts all active Satellite deployments (6.13, 6.14 and 6.15) and could potentially enable unauthorized users to gain administrative access. 披露时间: 2024-09-04 CVSS评分: 8.1 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-34640 漏洞描述: BGProtectManager在SMR Sep-2024版本之前的访问控制不当漏洞允许本地攻击者绕过进程过期限制。 披露时间: 2024-09-04 CVSS评分: 3.3 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-34637 漏洞描述: 在 Android 12 的 SMR Sep-2024 Release 1 以及 Android 13 和 Android 14 的 SMR Jun-2024 Release 1 中，WindowManagerService 存在不当的访问控制问题，这使得本地攻击者能够绕过后台启动服务的限制。 披露时间: 2024-09-04 CVSS评分: 6.2 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45448 漏洞描述: Huawei HarmonyOS是中国华为（Huawei）公司的一个操作系统。提供一个基于微内核的全场景分布式操作系统。 Huawei HarmonyOS存在安全漏洞，该漏洞源于可信固件模块存在页表保护配置漏洞。 披露时间: 2024-09-04 CVSS评分: 4.1 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-8298 漏洞描述: Huawei EMUI和Huawei HarmonyOS都是中国华为（Huawei）公司的产品。Huawei EMUI是一款基于Android开发的移动端操作系统。Huawei HarmonyOS是一个操作系统。提供一个基于微内核的全场景分布式操作系统。 HUAWEI HarmonyOS 4.2.0版本、4.0.0版本和EMUI 14.0.0版本存在安全漏洞，该漏洞源于内存管理不当。 披露时间: 2024-09-04 CVSS评分: 6.2 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-34647 漏洞描述: 在DualDarManagerProxy中特权API的不当使用，存在于早于SMR Sep-2024 Release 1的版本中，允许本地攻击者在没有适当许可证的情况下访问与Knox相关的特权API。 披露时间: 2024-09-04 CVSS评分: 4.0 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-34638 漏洞描述: 在SMR Sep-2024 Release 1之前的ThemeCenter中，异常条件的处理不当允许本地攻击者删除非预加载的应用程序。 披露时间: 2024-09-04 CVSS评分: 6.7 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-34644 漏洞描述: 在SMR Sep-2024版本发布之前的更衣室物品选择中存在不当的访问控制问题，允许本地攻击者访问受保护的数据。触发此漏洞需要用户进行交互。 披露时间: 2024-09-04 CVSS评分: 4.4 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-7923 漏洞描述: An authentication bypass vulnerability has been identified in Pulpcore when deployed with Gunicorn versions prior to 22.0, due to the puppet-pulpcore configuration. This issue arises from Apache's mod_proxy not properly unsetting headers because of restrictions on underscores in HTTP headers, allowing authentication through a malformed header. This flaw impacts all active Satellite deployments (6.13, 6.14 and 6.15) which are using Pulpcore version 3.0+ and could potentially enable unauthorized users to gain administrative access. 披露时间: 2024-09-04 CVSS评分: 9.8 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-7950 漏洞描述: WordPress的Job门户插件（一个为公司或招聘网站提供的完整招聘系统插件）存在本地文件包含漏洞、任意设置更新漏洞和用户创建漏洞。这些漏洞存在于版本2.1.6及以下的所有版本中，通过名为“checkFormRequest”的函数调用的几个函数引发。这使得未经身份验证的攻击者能够在服务器上包含和执行任意文件，允许在这些文件中执行任何PHP代码。这可以用于绕过访问控制，获取敏感数据，或者在可以上传和包含图像和其他“安全”文件类型的情况下实现代码执行。此外，攻击者还可以更新任意设置，甚至在禁用注册的情况下创建用户帐户，导致以管理员为默认角色的用户创建。 披露时间: 2024-09-04 CVSS评分: 9.8 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-34641 漏洞描述: SAMSUNG Mobile devices是韩国三星（SAMSUNG）公司的一系列的三星移动设备，包括手机、平板等。 SAMSUNG Mobile devices SMR Sep-2024 Release 1 版本及之前版本存在安全漏洞，该漏洞源于 FeliCaTest 组件包含一个Android 应用组件导出不当问题。 披露时间: 2024-09-04 CVSS评分: 5.1 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-34642 漏洞描述: One UI Home在SMR Sep-2024 Release 1之前的版本中存在不当授权问题，使得物理攻击者能够暂时访问敏感信息。 披露时间: 2024-09-04 CVSS评分: 4.6 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-34639 漏洞描述: 在SMR Aug-2024发布版本之前的Setupwizard异常条件处理不当，使得物理攻击者能够绕过适当的验证。 披露时间: 2024-09-04 CVSS评分: 4.6 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45449 漏洞描述: Huawei HarmonyOS是中国华为（Huawei）公司的一个操作系统。提供一个基于微内核的全场景分布式操作系统。 Huawei HarmonyOS存在安全漏洞，该漏洞源于设置铃声模块存在访问权限漏洞。 披露时间: 2024-09-04 CVSS评分: 5.1 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45445 漏洞描述: Huawei HarmonyOS是中国华为（Huawei）公司的一个操作系统。提供一个基于微内核的全场景分布式操作系统。 Huawei HarmonyOS存在安全漏洞，该漏洞源于keystore存在资源未关闭或释放漏洞。 披露时间: 2024-09-04 CVSS评分: 4.0 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45447 漏洞描述: Huawei HarmonyOS是中国华为（Huawei）公司的一个操作系统。提供一个基于微内核的全场景分布式操作系统。 Huawei HarmonyOS存在安全漏洞，该漏洞源于相机框架模块存在访问控制漏洞。 披露时间: 2024-09-04 CVSS评分: 4.4 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45507 漏洞描述: Apache OFBiz是一个电子商务平台，用于构建大中型企业级、跨平台、跨数据库、跨应用服务器的多层、分布式电子商务类应用系统。2024年9月，官方发布新版本修复了 CVE-2024-45507 Apache OFBiz SSRF致代码执行漏洞，攻击者可构造恶意请求控制服务器。建议尽快修复漏洞。 披露时间: 2024-09-04 CVSS评分: 8.1 解决方案: 官方已发布 18.12.16 ，建议升级至18.12.16及其以上版本。
CVE编号: CVE-2024-45446 漏洞描述: Huawei HarmonyOS是中国华为（Huawei）公司的一个操作系统。提供一个基于微内核的全场景分布式操作系统。 Huawei HarmonyOS存在安全漏洞，该漏洞源于Camera驱动模块存在访问权限漏洞。 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45443 漏洞描述: Huawei HarmonyOS是中国华为（Huawei）公司的一个操作系统。提供一个基于微内核的全场景分布式操作系统。 Huawei HarmonyOS存在安全漏洞，该漏洞源于cust模块存在目录穿越漏洞。 披露时间: 2024-09-04 CVSS评分: 6.1 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45444 漏洞描述: Huawei HarmonyOS是中国华为（Huawei）公司的一个操作系统。提供一个基于微内核的全场景分布式操作系统。 Huawei HarmonyOS存在安全漏洞，该漏洞源于WMS模块存在访问权限漏洞。 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45442 漏洞描述: Huawei HarmonyOS是中国华为（Huawei）公司的一个操作系统。提供一个基于微内核的全场景分布式操作系统。 Huawei HarmonyOS存在安全漏洞，该漏洞源于DownloadProviderMain模块存在接口权限校验类漏洞。 披露时间: 2024-09-04 CVSS评分: 5.1 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-39921 漏洞描述: Fujitsu IPCOM EX2是日本富士通（Fujitsu）公司的一系列网络设备。 IPCOM EX2存在安全漏洞，该漏洞源于存在信息泄露问题，一些加密通信可能会被可以获得通信内容的攻击者解密。 披露时间: 2024-09-04 CVSS评分: N/A 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45441 漏洞描述: Huawei EMUI和Huawei HarmonyOS都是中国华为（Huawei）公司的产品。Huawei EMUI是一款基于Android开发的移动端操作系统。Huawei HarmonyOS是一个操作系统。提供一个基于微内核的全场景分布式操作系统。 Huawei EMUI和Huawei HarmonyOS存在安全漏洞，该漏洞源于系统服务模块中的输入验证不当。以下产品及版本受到影响：HarmonyOS 4.2.0版本、HarmonyOS 2.0.0版本、HarmonyOS 2.1.0版本、HarmonyOS 3.0.0版本、HarmonyOS 3.1.0版本、HarmonyOS 4.0.0版本、EMUI 14.0.0版本、EMUI 13.0.0版本和EMUI 12.0.0版本。 披露时间: 2024-09-04 CVSS评分: 6.2 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45450 漏洞描述: Huawei EMUI和Huawei HarmonyOS都是中国华为（Huawei）公司的产品。Huawei EMUI是一款基于Android开发的移动端操作系统。Huawei HarmonyOS是一个操作系统。提供一个基于微内核的全场景分布式操作系统。 Huawei EMUI和Huawei HarmonyOS存在安全漏洞，该漏洞源于软件更新模块中的权限控制问题，成功利用此漏洞可能会影响服务机密性。以下产品及版本受到影响：HarmonyOS 4.2.0版本、HarmonyOS 2.0.0版本、HarmonyOS 2.1.0版本、HarmonyOS 3.0.0版本、HarmonyOS 3.1.0版本、HarmonyOS 4.0.0版本、EMUI 14.0.0版本、EMUI 13.0.0版本和EMUI 12.0.0版本。 披露时间: 2024-09-04 CVSS评分: 4.0 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-8362 漏洞描述: Google Chrome是谷歌开发的开源浏览器，Web Audio API模块用于处理和生成复杂的音频效果。 受影响版本中，AudioParamHandler类中DelayHandler::Process函数在处理音频数据时，没有对automation_rate_进行有效的锁定保护，导致UAF漏洞。 修复版本中，通过在访问automation_rate_时引入互斥锁，确保线程安全以修复漏洞。 披露时间: 2024-09-04 CVSS评分: 6.6 解决方案: "将组件 chromium 升级至 128.0.6613.119 及以上版本" "将组件 chrome 升级至 128.0.6613.119 及以上版本"
CVE编号: CVE-2024-45394 漏洞描述: Authenticator是一款生成双重身份验证码的浏览器扩展程序。在7.0.0及以下版本中，用户数据的加密密钥以静态形式存储时仅使用AES-256和EVP_BytesToKey密钥派生函数进行加密。因此，拥有用户数据副本的攻击者能够强行破解用户的加密密钥。对于使用版本8.0.0及以上的用户，在首次登录时会自动迁移到更强大的编码方式。用户应销毁使用版本低于8.0.0的加密备份。 披露时间: 2024-09-04 CVSS评分: 8.8 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-41927 漏洞描述: IDEC PLC是IDEC公司的一系列可编程控制器。 IDEC PLC多款产品存在安全漏洞，该漏洞源于敏感信息的明文传输。当攻击者向PLC的串行通信端口发送特定命令时，可能会获取到用户凭证，进而获得PLC程序并操控PLC。以下产品及版本受到影响：FC6A Series MICROSmart All-in-One CPU module Ver.2.60及之前版本、FC6B Series MICROSmart All-in-One CPU module Ver.2.60及之前版本、FC6A Series MICROSmart Plus CPU module Ver.2.40及之前版本、FC6B Series MICROSmart Plus CPU module Ver.2.60及之前版本、FT1A Series SmartAXIS Pro/Lite Ver.2.41及之前版本。 披露时间: 2024-09-04 CVSS评分: N/A 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-8418 漏洞描述: A flaw was found in Aardvark-dns versions 1.12.0 and 1.12.1. They contain a denial of service vulnerability due to serial processing of TCP DNS queries. This flaw allows a malicious client to keep a TCP connection open indefinitely, causing other DNS queries to time out and resulting in a denial of service for all other containers using aardvark-dns. 披露时间: 2024-09-04 CVSS评分: 6.2 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-41716 漏洞描述: IDEC WindLDR和WindO/I-NV4都是日本IDEC公司的产品。WindLDR是一个PLC 编程软件。WindO/I-NV4是操作员界面的触摸屏编程软件。 WindLDR V9.1.0及之前版本、WindO/I-NV4 V3.0.1及之前版本存在安全漏洞，该漏洞源于以明文形式存储敏感信息，远程攻击者可以未经授权访问系统上的敏感信息。 披露时间: 2024-09-04 CVSS评分: N/A 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44809 漏洞描述: camera-pi是Michael Horne个人开发者的一个相机模块。 camera-pi 1.0版本存在安全漏洞，该漏洞源于tilt.php脚本中对传递给position GET参数的用户输入处理不当，可能导致攻击者通过发送精心构造的包含恶意命令的数据来执行任意命令。 披露时间: 2024-09-04 CVSS评分: 9.8 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-41433 漏洞描述: PingCAP TiDB是中国PingCAP公司的一个开源、云原生、分布式、兼容 MySQL 的数据库，用于弹性扩展和实时分析。 PingCAP TiDB v8.1.0版本存在安全漏洞，该漏洞源于 expression.ExplainExpressionList 组件包含一个缓冲区溢出问题。 披露时间: 2024-09-04 CVSS评分: 9.8 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-42039 漏洞描述: Huawei HarmonyOS是中国华为（Huawei）公司的一个操作系统。提供一个基于微内核的全场景分布式操作系统。 Huawei HarmonyOS存在安全漏洞，该漏洞源于SystemUI模块存在访问控制漏洞。 披露时间: 2024-09-04 CVSS评分: 4.3 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-41436 漏洞描述: ClickHouse是一个用于联机分析处理（OLAP）的开源列式数据库。 受影响版本在通过allow_experimental_analyzer启用新分析器后，DB::evaluateConstantExpressionImpl仍然调用旧分析器导致溢出，攻击者可以通过构造特定的SQL插入语句进行DOS攻击。 修复版本中，通过在InterpreterSelectQuery和StorageDistributed中增加对查询树的检查和处理逻辑以修复漏洞。 披露时间: 2024-09-04 CVSS评分: 7.5 解决方案: "将组件 clickhouse 升级至 24.3.5.46 及以上版本"
CVE编号: CVE-2024-45391 漏洞描述: Tina是一个开源的内容管理系统（CMS）。在版本1.6.2之前，使用Tina CMS命令行接口（CLI）构建网站并在搜索中使用令牌的用户可能会面临通过锁定文件（tina-lock.json）泄露搜索令牌的风险。拥有搜索设置的Tina网站的管理员应立即更改其密钥。这个问题已在@tinacms/cli版本1.6.2中得到修复。为了正确修复，需要升级并更改搜索令牌。 披露时间: 2024-09-04 CVSS评分: 6.2 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-8399 漏洞描述: Mozilla Focus是美国Mozilla基金会的一个供iOS设备专用的浏览器。 Mozilla Focus 130之前版本存在安全漏洞，该漏洞源于网站可以利用 Javascript 链接来伪造 Focus 导航栏中的 URL 地址。 披露时间: 2024-09-04 CVSS评分: 4.7 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45389 漏洞描述: Pagefind是一个完全静态的搜索库，它根据用户加载的第一个脚本的位置来初始化其动态JavaScript和WebAssembly文件。此信息是通过查找`document.currentScript.src`的值来收集的。在Pagefind版本1.1.1之前，有可能通过页面上的其他良性HTML来“覆盖”此查找。这将导致`document.currentScript.src`解析为外部域，然后Pagefind会使用该域加载依赖项。这种攻击只有在攻击者能够向实时托管网站注入HTML的情况下才会起作用。在这种情况下，这将作为提升攻击者可用特权的一种方式。这假设他们有向页面添加某些元素的能力（例如带有名称属性的img标签），但不能添加其他元素，因为向页面添加脚本本身将是跨站脚本攻击向量。Pagefind在版本1.1.1中通过确保源是从有效脚本元素加载的来加强了这种解析。目前没有报告通过Pagefind在野外利用此漏洞的情况。 披露时间: 2024-09-04 CVSS评分: 6.0 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45307 漏洞描述: SudoBot是一款用于Discord社区管理的机器人，在版本低于9.26.7的情况下存在权限提升和“-config”命令漏洞风险。理论上任何人都可以更新该机器人的任何配置，从而可能控制机器人的设置。所有版本号为v9且低于v9.26.7的版本都会受到影响。其他版本（如v8）不受影响。用户应升级到版本9.26.7以获取补丁。一种解决方法是在数据库中创建命令权限覆盖。GitHub安全顾问提供了可执行的SQL语句，用于创建一个覆盖，禁止没有“管理公会”权限的用户运行“-config”命令。请在机器人所在的每个服务器上运行SQL语句，并将每次的"<公会ID>"替换为相应的公会ID。 披露时间: 2024-09-04 CVSS评分: 8.8 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45678 漏洞描述: Yubico YubiKey 5是Yubico公司的一款多协议安全秘钥设备。 Yubico YubiKey 5 5.7.0之前版本和YubiHSM 2 2.4.0之前版本存在安全漏洞，该漏洞源于扩展欧几里得算法中的非恒定时间模逆运算导致的电磁侧信道，可能允许具有物理访问权限并使用专业设备的攻击者进行ECDSA秘密密钥提取攻击。 披露时间: 2024-09-04 CVSS评分: 4.2 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-41434 漏洞描述: PingCAP TiDB是中国PingCAP公司的一个开源、云原生、分布式、兼容 MySQL 的数据库，用于弹性扩展和实时分析。 PingCAP TiDB v8.1.0版本存在安全漏洞，该漏洞源于 (*Column).GetDecimal 组件包含一个缓冲区溢出问题。 披露时间: 2024-09-04 CVSS评分: 4.3 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-43413 漏洞描述: Xibo是一个开源的数字标牌平台，具有网页内容管理系统（CMS）。在版本4.1.0之前，Xibo CMS中存在跨站脚本漏洞，授权用户可以通过数据集功能执行JavaScript。用户可以使用包含JavaScript的HTML列设计数据集，这是预期的功能。JavaScript将在数据输入页面和执行任何引用它的布局中执行。在4.1.0版本中，此行为已更改为在数据输入页面上显示HTML/CSS/JS作为代码。此问题没有解决方法。 披露时间: 2024-09-04 CVSS评分: 3.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45180 漏洞描述: SquaredUp DS for SCOM是SquaredUp公司的一个适用于 SCOM 的 SquaredUp 仪表板服务器。 SquaredUp DS for SCOM 6.2.1.11104版本存在安全漏洞，该漏洞源于容易受到跨站脚本攻击。 披露时间: 2024-09-04 CVSS评分: N/A 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45390 漏洞描述: @blakeembrey/template 是一个字符串模板库。在版本 1.2.0 之前，如果攻击者能够访问并写入模板名称，那么他们有可能在模板中注入并执行代码。版本 1.2.0 包含了一个补丁。作为解决方案，不要将不受信任的输出作为模板显示名称，或者不要使用显示名称功能。 披露时间: 2024-09-04 CVSS评分: 6.0 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-7970 漏洞描述: Google Chrome 是谷歌公司开发的浏览器，V8 是开源的 JavaScript 引擎。 受影响版本中，当 V8 引擎同时使用 Scavenger 和 Mark-Compact 垃圾回收算法时会造成内存越界写入，攻击者可诱导用户访问恶意网页窃取浏览器敏感信息或远程代码执行。 披露时间: 2024-09-04 CVSS评分: 6.6 解决方案: "将组件 chromium 升级至 128.0.6613.119 及以上版本" "将组件 chrome 升级至 128.0.6613.119 及以上版本" "将组件 v8 升级至 13.0.86 及以上版本"
CVE编号: CVE-2024-7619 漏洞描述: Rejected reason: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that there was not reasonable evidence to determine the existence of a vulnerability. 披露时间: 2024-09-04 CVSS评分: N/A 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-41435 漏洞描述: YugabyteDB是美国Yugabyte公司的一款用于云原生应用程序的高性能事务性分布式 SQL 数据库。 YugabyteDB v2.21.1.0版本存在安全漏洞，该漏洞源于insert into参数存在缓冲区溢出问题。 披露时间: 2024-09-04 CVSS评分: 7.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-43803 漏洞描述: Bare Metal Operator（BMO）在Metal3中实现了用于管理裸金属主机的Kubernetes API。`BareMetalHost`（BMH）CRD允许将托管主机的`userData`、`metaData`和`networkData`指定为指向Kubernetes Secrets的链接。对于Secret的`Name`和`Namespace`都有相应的字段，这意味着在版本低于0.8.0、0.6.2和0.5.2的baremetal-operator会从任何命名空间读取Secret。能够创建或编辑`BareMetalHost`的用户可以通过将其作为托管主机的`userData`（注意，这不必是真实的主机，也可以是某个地方的虚拟机）来从另一个命名空间中提取`Secret`。BMO只会读取名为`value`（或`userData`、`metaData`或`networkData`）的密钥，因此这在一定程度上限制了暴露。尽管`value`是一个相当常见的密钥，但由其他命名空间中的其他`BareMetalHost`使用的Secrets始终存在风险。除了集群管理员之外，拥有创建/编辑`BareMetalHost`的RBAC访问权限的其他人可能很少见。如果集群中存在除管理员之外的用户，并且用户的权限仅限于其各自的命名空间，那么这个漏洞才有意义。补丁阻止了BMO接受来自其他命名空间的Secrets链接作为BMH输入。任何BMH配置只能从相同的命名空间中读取。这个问题已在BMO v0.7.0、v0.6.2和v0.5.2版本中修复，用户应升级到这些版本。在升级之前，请将BMC Secrets复制到相应的BMH所在的命名空间。升级后，删除旧的Secrets。作为一种解决方法，操作员可以配置BMO RBAC为Secrets进行命名空间范围限定，而不是集群范围限定，以防止BMO访问其他命名空间的Secrets。 披露时间: 2024-09-04 CVSS评分: 4.3 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-42902 漏洞描述: LimeSurvey（PHPSurveyor）是LimeSurvey团队的一套开源的在线问卷调查程序，它支持调查程序开发、调查问卷发布以及数据收集等功能。 LimeSurvey v6.6.2版本及之前版本存在安全漏洞，该漏洞源于js_localize.php函数的lng参数包含一个任意代码执行漏洞。 披露时间: 2024-09-04 CVSS评分: 8.8 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-42903 漏洞描述: LimeSurvey（PHPSurveyor）是LimeSurvey团队的一套开源的在线问卷调查程序，它支持调查程序开发、调查问卷发布以及数据收集等功能。 LimeSurvey v.6.6.1+240806版本及之前版本存在安全漏洞，该漏洞源于密码重置功能中存在主机头注入问题，允许攻击者向用户发送特制的密码重置链接，该链接会将受害者引导至恶意域。 披露时间: 2024-09-04 CVSS评分: 6.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-6119 漏洞描述: 问题概述：应用程序执行证书名称检查（例如，TLS客户端检查服务器证书）时，可能会尝试读取无效的内存地址，导致应用程序进程异常终止。影响概述：应用程序的异常终止可能会导致拒绝服务。在进行证书名称检查的应用程序（例如，TLS客户端检查服务器证书）中，当将预期名称与X.509证书的`otherName`主题替代名称进行比较时，可能会尝试读取无效的内存地址。这可能会导致异常并终止应用程序程序。请注意，基本证书链验证（签名、日期等）不受影响，拒绝服务的情况仅会在应用程序还指定预期的DNS名称、电子邮件地址或IP地址时发生。TLS服务器很少请求客户端证书，即使它们这样做，通常也不会针对参考标识符（预期身份）执行名称检查，而是在检查证书链后提取显示的身份。因此，TLS服务器通常不受影响，此问题的严重性为中等。在3.3、3.2、3.1和3.0版本中的FIPS模块不受此问题影响。 披露时间: 2024-09-04 CVSS评分: 6.2 解决方案: "将组件 OpenSSL 升级至 3.3.2 及以上版本" "将组件 OpenSSL 升级至 3.2.3 及以上版本" "将组件 OpenSSL 升级至 3.0.15 及以上版本" "将组件 OpenSSL 升级至 3.1.7 及以上版本"
CVE编号: CVE-2024-43412 漏洞描述: Xibo是一个开源的数字标牌平台，具有网页内容管理系统（CMS）。在版本4.1.0之前，Xibo CMS中存在跨站脚本漏洞，授权用户可以通过文件预览功能执行任意JavaScript。用户可以通过通用文件模块将HTML/CSS/JS文件上传到Xibo库中，以便在显示和布局中引用。这是预期的功能。在预览库和布局编辑器中的这些资源时，它们会在用户的浏览器中执行。未来版本中将禁用此功能，并鼓励用户使用4.1中的新开发工具设计需要此类功能的控件。在4.1.0版本中，通用文件的预览行为已经更改。此问题没有解决方法。 披露时间: 2024-09-04 CVSS评分: 4.6 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2023-49233 漏洞描述: Visual Planning Admin Center是Visual Planning公司的一款基于云的资源管理和调度软件。 Visual Planning Admin Center 8（Build 240207）之前版本存在安全漏洞，该漏洞源于访问检查不足。攻击者利用该漏洞可以获取不同类型的配置凭据。 披露时间: 2024-09-04 CVSS评分: 8.8 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-42904 漏洞描述: sysPass是RubénD个人开发者的一个系统密码管理器。 sysPass 3.2.x版本存在安全漏洞，该漏洞源于容易受到跨站脚本攻击。攻击者利用该漏洞通过将特制的有效载荷注入到/Controllers/ClientController.php的name参数来执行任意Web脚本或HTML。 披露时间: 2024-09-04 CVSS评分: 6.1 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-38456 漏洞描述: Vivavis是Vivavis公司的一个自动化控制系统。 Vivavis存在权限许可和访问控制问题漏洞，该漏洞源于prunsrv.exe中包含一个授权问题，可能导致任意代码执行。 披露时间: 2024-09-04 CVSS评分: 7.8 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-42901 漏洞描述: LimeSurvey（PHPSurveyor）是LimeSurvey团队的一套开源的在线问卷调查程序，它支持调查程序开发、调查问卷发布以及数据收集等功能。 LimeSurvey v6.5.12版本存在安全漏洞，该漏洞源于包含一个 CSV 注入漏洞。 披露时间: 2024-09-04 CVSS评分: 4.8 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45005 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: KVM: s390: fix validity interception issue when gisa is switched off We might run into a SIE validity if gisa has been disabled either via using kernel parameter "kvm.use_gisa=0" or by setting the related sysfs attribute to N (echo N >/sys/module/kvm/parameters/use_gisa). The validity is caused by an invalid value in the SIE control block's gisa designation. That happens because we pass the uninitialized gisa origin to virt_to_phys() before writing it to the gisa designation. To fix this we return 0 in kvm_s390_get_gisa_desc() if the origin is 0. kvm_s390_get_gisa_desc() is used to determine which gisa designation to set in the SIE control block. A value of 0 in the gisa designation disables gisa usage. The issue surfaces in the host kernel with the following kernel message as soon a new kvm guest start is attemted. kvm: unhandled validity intercept 0x1011 WARNING: CPU: 0 PID: 781237 at arch/s390/kvm/intercept.c:101 kvm_handle_sie_intercept+0x42e/0x4d0 [kvm] Modules linked in: vhost_net tap tun xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT xt_tcpudp nft_compat x_tables nf_nat_tftp nf_conntrack_tftp vfio_pci_core irqbypass vhost_vsock vmw_vsock_virtio_transport_common vsock vhost vhost_iotlb kvm nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables sunrpc mlx5_ib ib_uverbs ib_core mlx5_core uvdevice s390_trng eadm_sch vfio_ccw zcrypt_cex4 mdev vfio_iommu_type1 vfio sch_fq_codel drm i2c_core loop drm_panel_orientation_quirks configfs nfnetlink lcs ctcm fsm dm_service_time ghash_s390 prng chacha_s390 libchacha aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common dm_mirror dm_region_hash dm_log zfcp scsi_transport_fc scsi_dh_rdac scsi_dh_emc scsi_dh_alua pkey zcrypt dm_multipath rng_core autofs4 [last unloaded: vfio_pci] CPU: 0 PID: 781237 Comm: CPU 0/KVM Not tainted 6.10.0-08682-gcad9f11498ea #6 Hardware name: IBM 3931 A01 701 (LPAR) Krnl PSW : 0704c00180000000 000003d93deb0122 (kvm_handle_sie_intercept+0x432/0x4d0 [kvm]) R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 Krnl GPRS: 000003d900000027 000003d900000023 0000000000000028 000002cd00000000 000002d063a00900 00000359c6daf708 00000000000bebb5 0000000000001eff 000002cfd82e9000 000002cfd80bc000 0000000000001011 000003d93deda412 000003ff8962df98 000003d93de77ce0 000003d93deb011e 00000359c6daf960 Krnl Code: 000003d93deb0112: c020fffe7259 larl %r2,000003d93de7e5c4 000003d93deb0118: c0e53fa8beac brasl %r14,000003d9bd3c7e70 #000003d93deb011e: af000000 mc 0,0 >000003d93deb0122: a728ffea lhi %r2,-22 000003d93deb0126: a7f4fe24 brc 15,000003d93deafd6e 000003d93deb012a: 9101f0b0 tm 176(%r15),1 000003d93deb012e: a774fe48 brc 7,000003d93deafdbe 000003d93deb0132: 40a0f0ae sth %r10,174(%r15) Call Trace: [<000003d93deb0122>] kvm_handle_sie_intercept+0x432/0x4d0 [kvm] ([<000003d93deb011e>] kvm_handle_sie_intercept+0x42e/0x4d0 [kvm]) [<000003d93deacc10>] vcpu_post_run+0x1d0/0x3b0 [kvm] [<000003d93deaceda>] __vcpu_run+0xea/0x2d0 [kvm] [<000003d93dead9da>] kvm_arch_vcpu_ioctl_run+0x16a/0x430 [kvm] [<000003d93de93ee0>] kvm_vcpu_ioctl+0x190/0x7c0 [kvm] [<000003d9bd728b4e>] vfs_ioctl+0x2e/0x70 [<000003d9bd72a092>] __s390x_sys_ioctl+0xc2/0xd0 [<000003d9be0e9222>] __do_syscall+0x1f2/0x2e0 [<000003d9be0f9a90>] system_call+0x70/0x98 Last Breaking-Event-Address: [<000003d9bd3c7f58>] __warn_printk+0xe8/0xf0 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45002 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: rtla/osnoise: Prevent NULL dereference in error handling If the "tool->data" allocation fails then there is no need to call osnoise_free_top() and, in fact, doing so will lead to a NULL dereference. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45001 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: net: mana: Fix RX buf alloc_size alignment and atomic op panic The MANA driver's RX buffer alloc_size is passed into napi_build_skb() to create SKB. skb_shinfo(skb) is located at the end of skb, and its alignment is affected by the alloc_size passed into napi_build_skb(). The size needs to be aligned properly for better performance and atomic operations. Otherwise, on ARM64 CPU, for certain MTU settings like 4000, atomic operations may panic on the skb_shinfo(skb)->dataref due to alignment fault. To fix this bug, add proper alignment to the alloc_size calculation. Sample panic info: [ 253.298819] Unable to handle kernel paging request at virtual address ffff000129ba5cce [ 253.300900] Mem abort info: [ 253.301760] ESR = 0x0000000096000021 [ 253.302825] EC = 0x25: DABT (current EL), IL = 32 bits [ 253.304268] SET = 0, FnV = 0 [ 253.305172] EA = 0, S1PTW = 0 [ 253.306103] FSC = 0x21: alignment fault Call trace: __skb_clone+0xfc/0x198 skb_clone+0x78/0xe0 raw6_local_deliver+0xfc/0x228 ip6_protocol_deliver_rcu+0x80/0x500 ip6_input_finish+0x48/0x80 ip6_input+0x48/0xc0 ip6_sublist_rcv_finish+0x50/0x78 ip6_sublist_rcv+0x1cc/0x2b8 ipv6_list_rcv+0x100/0x150 __netif_receive_skb_list_core+0x180/0x220 netif_receive_skb_list_internal+0x198/0x2a8 __napi_poll+0x138/0x250 net_rx_action+0x148/0x330 handle_softirqs+0x12c/0x3a0 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-42991 漏洞描述: MingSoft MCMS是中国铭飞（MingSoft）公司的一个完整开源的 J2ee 系统。 MingSoft MCMS v5.4.1版本存在安全漏洞，该漏洞源于前端文件上传功能的不当处理，可能导致远程命令执行。 披露时间: 2024-09-04 CVSS评分: 8.1 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-8443 漏洞描述: No description is available for this CVE. 披露时间: 2024-09-04 CVSS评分: 3.4 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45000 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: fs/netfs/fscache_cookie: add missing "n_accesses" check This fixes a NULL pointer dereference bug due to a data race which looks like this: BUG: kernel NULL pointer dereference, address: 0000000000000008 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] SMP PTI CPU: 33 PID: 16573 Comm: kworker/u97:799 Not tainted 6.8.7-cm4all1-hp+ #43 Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 10/17/2018 Workqueue: events_unbound netfs_rreq_write_to_cache_work RIP: 0010:cachefiles_prepare_write+0x30/0xa0 Code: 57 41 56 45 89 ce 41 55 49 89 cd 41 54 49 89 d4 55 53 48 89 fb 48 83 ec 08 48 8b 47 08 48 83 7f 10 00 48 89 34 24 48 8b 68 20 <48> 8b 45 08 4c 8b 38 74 45 49 8b 7f 50 e8 4e a9 b0 ff 48 8b 73 10 RSP: 0018:ffffb4e78113bde0 EFLAGS: 00010286 RAX: ffff976126be6d10 RBX: ffff97615cdb8438 RCX: 0000000000020000 RDX: ffff97605e6c4c68 RSI: ffff97605e6c4c60 RDI: ffff97615cdb8438 RBP: 0000000000000000 R08: 0000000000278333 R09: 0000000000000001 R10: ffff97605e6c4600 R11: 0000000000000001 R12: ffff97605e6c4c68 R13: 0000000000020000 R14: 0000000000000001 R15: ffff976064fe2c00 FS: 0000000000000000(0000) GS:ffff9776dfd40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000008 CR3: 000000005942c002 CR4: 00000000001706f0 Call Trace: <TASK> ? __die+0x1f/0x70 ? page_fault_oops+0x15d/0x440 ? search_module_extables+0xe/0x40 ? fixup_exception+0x22/0x2f0 ? exc_page_fault+0x5f/0x100 ? asm_exc_page_fault+0x22/0x30 ? cachefiles_prepare_write+0x30/0xa0 netfs_rreq_write_to_cache_work+0x135/0x2e0 process_one_work+0x137/0x2c0 worker_thread+0x2e9/0x400 ? __pfx_worker_thread+0x10/0x10 kthread+0xcc/0x100 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x30/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 </TASK> Modules linked in: CR2: 0000000000000008 ---[ end trace 0000000000000000 ]--- This happened because fscache_cookie_state_machine() was slow and was still running while another process invoked fscache_unuse_cookie(); this led to a fscache_cookie_lru_do_one() call, setting the FSCACHE_COOKIE_DO_LRU_DISCARD flag, which was picked up by fscache_cookie_state_machine(), withdrawing the cookie via cachefiles_withdraw_cookie(), clearing cookie->cache_priv. At the same time, yet another process invoked cachefiles_prepare_write(), which found a NULL pointer in this code line: struct cachefiles_object *object = cachefiles_cres_object(cres); The next line crashes, obviously: struct cachefiles_cache *cache = object->volume->cache; During cachefiles_prepare_write(), the "n_accesses" counter is non-zero (via fscache_begin_operation()). The cookie must not be withdrawn until it drops to zero. The counter is checked by fscache_cookie_state_machine() before switching to FSCACHE_COOKIE_STATE_RELINQUISHING and FSCACHE_COOKIE_STATE_WITHDRAWING (in "case FSCACHE_COOKIE_STATE_FAILED"), but not for FSCACHE_COOKIE_STATE_LRU_DISCARDING ("case FSCACHE_COOKIE_STATE_ACTIVE"). This patch adds the missing check. With a non-zero access counter, the function returns and the next fscache_end_cookie_access() call will queue another fscache_cookie_state_machine() call to handle the still-pending FSCACHE_COOKIE_DO_LRU_DISCARD. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45007 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: char: xillybus: Don't destroy workqueue from work item running on it Triggered by a kref decrement, destroy_workqueue() may be called from within a work item for destroying its own workqueue. This illegal situation is averted by adding a module-global workqueue for exclusive use of the offending work item. Other work items continue to be queued on per-device workqueues to ensure performance. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44996 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: vsock: fix recursive ->recvmsg calls After a vsock socket has been added to a BPF sockmap, its prot->recvmsg has been replaced with vsock_bpf_recvmsg(). Thus the following recursiion could happen: vsock_bpf_recvmsg() -> __vsock_recvmsg() -> vsock_connectible_recvmsg() -> prot->recvmsg() -> vsock_bpf_recvmsg() again We need to fix it by calling the original ->recvmsg() without any BPF sockmap logic in __vsock_recvmsg(). 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45008 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: Input: MT - limit max slots syzbot is reporting too large allocation at input_mt_init_slots(), for num_slots is supplied from userspace using ioctl(UI_DEV_CREATE). Since nobody knows possible max slots, this patch chose 1024. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44995 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: net: hns3: fix a deadlock problem when config TC during resetting When config TC during the reset process, may cause a deadlock, the flow is as below: pf reset start │ ▼ ...... setup tc │ │ ▼ ▼ DOWN: napi_disable() napi_disable()(skip) │ │ │ ▼ ▼ ...... ...... │ │ ▼ │ napi_enable() │ ▼ UINIT: netif_napi_del() │ ▼ ...... │ ▼ INIT: netif_napi_add() │ ▼ ...... global reset start │ │ ▼ ▼ UP: napi_enable()(skip) ...... │ │ ▼ ▼ ...... napi_disable() In reset process, the driver will DOWN the port and then UINIT, in this case, the setup tc process will UP the port before UINIT, so cause the problem. Adds a DOWN process in UINIT to fix it. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44999 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: gtp: pull network headers in gtp_dev_xmit() syzbot/KMSAN reported use of uninit-value in get_dev_xmit() [1] We must make sure the IPv4 or Ipv6 header is pulled in skb->head before accessing fields in them. Use pskb_inet_may_pull() to fix this issue. [1] BUG: KMSAN: uninit-value in ipv6_pdp_find drivers/net/gtp.c:220 [inline] BUG: KMSAN: uninit-value in gtp_build_skb_ip6 drivers/net/gtp.c:1229 [inline] BUG: KMSAN: uninit-value in gtp_dev_xmit+0x1424/0x2540 drivers/net/gtp.c:1281 ipv6_pdp_find drivers/net/gtp.c:220 [inline] gtp_build_skb_ip6 drivers/net/gtp.c:1229 [inline] gtp_dev_xmit+0x1424/0x2540 drivers/net/gtp.c:1281 __netdev_start_xmit include/linux/netdevice.h:4913 [inline] netdev_start_xmit include/linux/netdevice.h:4922 [inline] xmit_one net/core/dev.c:3580 [inline] dev_hard_start_xmit+0x247/0xa20 net/core/dev.c:3596 __dev_queue_xmit+0x358c/0x5610 net/core/dev.c:4423 dev_queue_xmit include/linux/netdevice.h:3105 [inline] packet_xmit+0x9c/0x6c0 net/packet/af_packet.c:276 packet_snd net/packet/af_packet.c:3145 [inline] packet_sendmsg+0x90e3/0xa3a0 net/packet/af_packet.c:3177 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:745 __sys_sendto+0x685/0x830 net/socket.c:2204 __do_sys_sendto net/socket.c:2216 [inline] __se_sys_sendto net/socket.c:2212 [inline] __x64_sys_sendto+0x125/0x1d0 net/socket.c:2212 x64_sys_call+0x3799/0x3c10 arch/x86/include/generated/asm/syscalls_64.h:45 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:3994 [inline] slab_alloc_node mm/slub.c:4037 [inline] kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4080 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:583 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:674 alloc_skb include/linux/skbuff.h:1320 [inline] alloc_skb_with_frags+0xc8/0xbf0 net/core/skbuff.c:6526 sock_alloc_send_pskb+0xa81/0xbf0 net/core/sock.c:2815 packet_alloc_skb net/packet/af_packet.c:2994 [inline] packet_snd net/packet/af_packet.c:3088 [inline] packet_sendmsg+0x749c/0xa3a0 net/packet/af_packet.c:3177 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:745 __sys_sendto+0x685/0x830 net/socket.c:2204 __do_sys_sendto net/socket.c:2216 [inline] __se_sys_sendto net/socket.c:2212 [inline] __x64_sys_sendto+0x125/0x1d0 net/socket.c:2212 x64_sys_call+0x3799/0x3c10 arch/x86/include/generated/asm/syscalls_64.h:45 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 0 UID: 0 PID: 7115 Comm: syz.1.515 Not tainted 6.11.0-rc1-syzkaller-00043-g94ede2a3e913 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44994 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: iommu: Restore lost return in iommu_report_device_fault() When iommu_report_device_fault gets called with a partial fault it is supposed to collect the fault into the group and then return. Instead the return was accidently deleted which results in trying to process the fault and an eventual crash. Deleting the return was a typo, put it back. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45004 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: KEYS: trusted: dcp: fix leak of blob encryption key Trusted keys unseal the key blob on load, but keep the sealed payload in the blob field so that every subsequent read (export) will simply convert this field to hex and send it to userspace. With DCP-based trusted keys, we decrypt the blob encryption key (BEK) in the Kernel due hardware limitations and then decrypt the blob payload. BEK decryption is done in-place which means that the trusted key blob field is modified and it consequently holds the BEK in plain text. Every subsequent read of that key thus send the plain text BEK instead of the encrypted BEK to userspace. This issue only occurs when importing a trusted DCP-based key and then exporting it again. This should rarely happen as the common use cases are to either create a new trusted key and export it, or import a key blob and then just use it without exporting it again. Fix this by performing BEK decryption and encryption in a dedicated buffer. Further always wipe the plain text BEK buffer to prevent leaking the key via uninitialized memory. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44993 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Fix out-of-bounds read in `v3d_csd_job_run()` When enabling UBSAN on Raspberry Pi 5, we get the following warning: [ 387.894977] UBSAN: array-index-out-of-bounds in drivers/gpu/drm/v3d/v3d_sched.c:320:3 [ 387.903868] index 7 is out of range for type '__u32 [7]' [ 387.909692] CPU: 0 PID: 1207 Comm: kworker/u16:2 Tainted: G WC 6.10.3-v8-16k-numa #151 [ 387.919166] Hardware name: Raspberry Pi 5 Model B Rev 1.0 (DT) [ 387.925961] Workqueue: v3d_csd drm_sched_run_job_work [gpu_sched] [ 387.932525] Call trace: [ 387.935296] dump_backtrace+0x170/0x1b8 [ 387.939403] show_stack+0x20/0x38 [ 387.942907] dump_stack_lvl+0x90/0xd0 [ 387.946785] dump_stack+0x18/0x28 [ 387.950301] __ubsan_handle_out_of_bounds+0x98/0xd0 [ 387.955383] v3d_csd_job_run+0x3a8/0x438 [v3d] [ 387.960707] drm_sched_run_job_work+0x520/0x6d0 [gpu_sched] [ 387.966862] process_one_work+0x62c/0xb48 [ 387.971296] worker_thread+0x468/0x5b0 [ 387.975317] kthread+0x1c4/0x1e0 [ 387.978818] ret_from_fork+0x10/0x20 [ 387.983014] ---[ end trace ]--- This happens because the UAPI provides only seven configuration registers and we are reading the eighth position of this u32 array. Therefore, fix the out-of-bounds read in `v3d_csd_job_run()` by accessing only seven positions on the '__u32 [7]' array. The eighth register exists indeed on V3D 7.1, but it isn't currently used. That being so, let's guarantee that it remains unused and add a note that it could be set in a future patch. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44992 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: smb/client: avoid possible NULL dereference in cifs_free_subrequest() Clang static checker (scan-build) warning: cifsglob.h:line 890, column 3 Access to field 'ops' results in a dereference of a null pointer. Commit 519be989717c ("cifs: Add a tracepoint to track credits involved in R/W requests") adds a check for 'rdata->server', and let clang throw this warning about NULL dereference. When 'rdata->credits.value != 0 && rdata->server == NULL' happens, add_credits_and_wake_if() will call rdata->server->ops->add_credits(). This will cause NULL dereference problem. Add a check for 'rdata->server' to avoid NULL dereference. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44997 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb() When there are multiple ap interfaces on one band and with WED on, turning the interface down will cause a kernel panic on MT798X. Previously, cb_priv was freed in mtk_wed_setup_tc_block() without marking NULL,and mtk_wed_setup_tc_block_cb() didn't check the value, too. Assign NULL after free cb_priv in mtk_wed_setup_tc_block() and check NULL in mtk_wed_setup_tc_block_cb(). ---------- Unable to handle kernel paging request at virtual address 0072460bca32b4f5 Call trace: mtk_wed_setup_tc_block_cb+0x4/0x38 0xffffffc0794084bc tcf_block_playback_offloads+0x70/0x1e8 tcf_block_unbind+0x6c/0xc8 ... --------- 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45006 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration re-enumerating full-speed devices after a failed address device command can trigger a NULL pointer dereference. Full-speed devices may need to reconfigure the endpoint 0 Max Packet Size value during enumeration. Usb core calls usb_ep0_reinit() in this case, which ends up calling xhci_configure_endpoint(). On Panther point xHC the xhci_configure_endpoint() function will additionally check and reserve bandwidth in software. Other hosts do this in hardware If xHC address device command fails then a new xhci_virt_device structure is allocated as part of re-enabling the slot, but the bandwidth table pointers are not set up properly here. This triggers the NULL pointer dereference the next time usb_ep0_reinit() is called and xhci_configure_endpoint() tries to check and reserve bandwidth [46710.713538] usb 3-1: new full-speed USB device number 5 using xhci_hcd [46710.713699] usb 3-1: Device not responding to setup address. [46710.917684] usb 3-1: Device not responding to setup address. [46711.125536] usb 3-1: device not accepting address 5, error -71 [46711.125594] BUG: kernel NULL pointer dereference, address: 0000000000000008 [46711.125600] #PF: supervisor read access in kernel mode [46711.125603] #PF: error_code(0x0000) - not-present page [46711.125606] PGD 0 P4D 0 [46711.125610] Oops: Oops: 0000 [#1] PREEMPT SMP PTI [46711.125615] CPU: 1 PID: 25760 Comm: kworker/1:2 Not tainted 6.10.3_2 #1 [46711.125620] Hardware name: Gigabyte Technology Co., Ltd. [46711.125623] Workqueue: usb_hub_wq hub_event [usbcore] [46711.125668] RIP: 0010:xhci_reserve_bandwidth (drivers/usb/host/xhci.c Fix this by making sure bandwidth table pointers are set up correctly after a failed address device command, and additionally by avoiding checking for bandwidth in cases like this where no actual endpoints are added or removed, i.e. only context for default control endpoint 0 is evaluated. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-45003 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: vfs: Don't evict inode under the inode lru traversing context The inode reclaiming process(See function prune_icache_sb) collects all reclaimable inodes and mark them with I_FREEING flag at first, at that time, other processes will be stuck if they try getting these inodes (See function find_inode_fast), then the reclaiming process destroy the inodes by function dispose_list(). Some filesystems(eg. ext4 with ea_inode feature, ubifs with xattr) may do inode lookup in the inode evicting callback function, if the inode lookup is operated under the inode lru traversing context, deadlock problems may happen. Case 1: In function ext4_evict_inode(), the ea inode lookup could happen if ea_inode feature is enabled, the lookup process will be stuck under the evicting context like this: 1. File A has inode i_reg and an ea inode i_ea 2. getfattr(A, xattr_buf) // i_ea is added into lru // lru->i_ea 3. Then, following three processes running like this: PA PB echo 2 > /proc/sys/vm/drop_caches shrink_slab prune_dcache_sb // i_reg is added into lru, lru->i_ea->i_reg prune_icache_sb list_lru_walk_one inode_lru_isolate i_ea->i_state |= I_FREEING // set inode state inode_lru_isolate __iget(i_reg) spin_unlock(&i_reg->i_lock) spin_unlock(lru_lock) rm file A i_reg->nlink = 0 iput(i_reg) // i_reg->nlink is 0, do evict ext4_evict_inode ext4_xattr_delete_inode ext4_xattr_inode_dec_ref_all ext4_xattr_inode_iget ext4_iget(i_ea->i_ino) iget_locked find_inode_fast __wait_on_freeing_inode(i_ea) ----→ AA deadlock dispose_list // cannot be executed by prune_icache_sb wake_up_bit(&i_ea->i_state) Case 2: In deleted inode writing function ubifs_jnl_write_inode(), file deleting process holds BASEHD's wbuf->io_mutex while getting the xattr inode, which could race with inode reclaiming process(The reclaiming process could try locking BASEHD's wbuf->io_mutex in inode evicting function), then an ABBA deadlock problem would happen as following: 1. File A has inode ia and a xattr(with inode ixa), regular file B has inode ib and a xattr. 2. getfattr(A, xattr_buf) // ixa is added into lru // lru->ixa 3. Then, following three processes running like this: PA PB PC echo 2 > /proc/sys/vm/drop_caches shrink_slab prune_dcache_sb // ib and ia are added into lru, lru->ixa->ib->ia prune_icache_sb list_lru_walk_one inode_lru_isolate ixa->i_state |= I_FREEING // set inode state inode_lru_isolate __iget(ib) spin_unlock(&ib->i_lock) spin_unlock(lru_lock) rm file B ib->nlink = 0 rm file A iput(ia) ubifs_evict_inode(ia) ubifs_jnl_delete_inode(ia) ubifs_jnl_write_inode(ia) make_reservation(BASEHD) // Lock wbuf->io_mutex ubifs_iget(ixa->i_ino) iget_locked find_inode_fast __wait_on_freeing_inode(ixa) | iput(ib) // ib->nlink is 0, do evict | ubifs_evict_inode | ubifs_jnl_delete_inode(ib) ↓ ubifs_jnl_write_inode ABBA deadlock ←-----make_reservation(BASEHD) dispose_list // cannot be executed by prune_icache_sb wake_up_bit(&ixa->i_state) Fix the possible deadlock by using new inode state flag I_LRU_ISOLATING to pin the inode in memory while inode_lru_isolate( ---truncated--- 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44991 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: tcp: prevent concurrent execution of tcp_sk_exit_batch Its possible that two threads call tcp_sk_exit_batch() concurrently, once from the cleanup_net workqueue, once from a task that failed to clone a new netns. In the latter case, error unwinding calls the exit handlers in reverse order for the 'failed' netns. tcp_sk_exit_batch() calls tcp_twsk_purge(). Problem is that since commit b099ce2602d8 ("net: Batch inet_twsk_purge"), this function picks up twsk in any dying netns, not just the one passed in via exit_batch list. This means that the error unwind of setup_net() can "steal" and destroy timewait sockets belonging to the exiting netns. This allows the netns exit worker to proceed to call WARN_ON_ONCE(!refcount_dec_and_test(&net->ipv4.tcp_death_row.tw_refcount)); without the expected 1 -> 0 transition, which then splats. At same time, error unwind path that is also running inet_twsk_purge() will splat as well: WARNING: .. at lib/refcount.c:31 refcount_warn_saturate+0x1ed/0x210 ... refcount_dec include/linux/refcount.h:351 [inline] inet_twsk_kill+0x758/0x9c0 net/ipv4/inet_timewait_sock.c:70 inet_twsk_deschedule_put net/ipv4/inet_timewait_sock.c:221 inet_twsk_purge+0x725/0x890 net/ipv4/inet_timewait_sock.c:304 tcp_sk_exit_batch+0x1c/0x170 net/ipv4/tcp_ipv4.c:3522 ops_exit_list+0x128/0x180 net/core/net_namespace.c:178 setup_net+0x714/0xb40 net/core/net_namespace.c:375 copy_net_ns+0x2f0/0x670 net/core/net_namespace.c:508 create_new_namespaces+0x3ea/0xb10 kernel/nsproxy.c:110 ... because refcount_dec() of tw_refcount unexpectedly dropped to 0. This doesn't seem like an actual bug (no tw sockets got lost and I don't see a use-after-free) but as erroneous trigger of debug check. Add a mutex to force strict ordering: the task that calls tcp_twsk_purge() blocks other task from doing final _dec_and_test before mutex-owner has removed all tw sockets of dying netns. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44990 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: bonding: fix null pointer deref in bond_ipsec_offload_ok We must check if there is an active slave before dereferencing the pointer. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44998 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: atm: idt77252: prevent use after free in dequeue_rx() We can't dereference "skb" after calling vcc->push() because the skb is released. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44988 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: net: dsa: mv88e6xxx: Fix out-of-bound access If an ATU violation was caused by a CPU Load operation, the SPID could be larger than DSA_MAX_PORTS (the size of mv88e6xxx_chip.ports[] array). 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44984 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix double DMA unmapping for XDP_REDIRECT Remove the dma_unmap_page_attrs() call in the driver's XDP_REDIRECT code path. This should have been removed when we let the page pool handle the DMA mapping. This bug causes the warning: WARNING: CPU: 7 PID: 59 at drivers/iommu/dma-iommu.c:1198 iommu_dma_unmap_page+0xd5/0x100 CPU: 7 PID: 59 Comm: ksoftirqd/7 Tainted: G W 6.8.0-1010-gcp #11-Ubuntu Hardware name: Dell Inc. PowerEdge R7525/0PYVT1, BIOS 2.15.2 04/02/2024 RIP: 0010:iommu_dma_unmap_page+0xd5/0x100 Code: 89 ee 48 89 df e8 cb f2 69 ff 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d 31 c0 31 d2 31 c9 31 f6 31 ff 45 31 c0 e9 ab 17 71 00 <0f> 0b 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d 31 c0 31 d2 31 c9 RSP: 0018:ffffab1fc0597a48 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff99ff838280c8 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffab1fc0597a78 R08: 0000000000000002 R09: ffffab1fc0597c1c R10: ffffab1fc0597cd3 R11: ffff99ffe375acd8 R12: 00000000e65b9000 R13: 0000000000000050 R14: 0000000000001000 R15: 0000000000000002 FS: 0000000000000000(0000) GS:ffff9a06efb80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000565c34c37210 CR3: 00000005c7e3e000 CR4: 0000000000350ef0 ? show_regs+0x6d/0x80 ? __warn+0x89/0x150 ? iommu_dma_unmap_page+0xd5/0x100 ? report_bug+0x16a/0x190 ? handle_bug+0x51/0xa0 ? exc_invalid_op+0x18/0x80 ? iommu_dma_unmap_page+0xd5/0x100 ? iommu_dma_unmap_page+0x35/0x100 dma_unmap_page_attrs+0x55/0x220 ? bpf_prog_4d7e87c0d30db711_xdp_dispatcher+0x64/0x9f bnxt_rx_xdp+0x237/0x520 [bnxt_en] bnxt_rx_pkt+0x640/0xdd0 [bnxt_en] __bnxt_poll_work+0x1a1/0x3d0 [bnxt_en] bnxt_poll+0xaa/0x1e0 [bnxt_en] __napi_poll+0x33/0x1e0 net_rx_action+0x18a/0x2f0 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44989 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: bonding: fix xfrm real_dev null pointer dereference We shouldn't set real_dev to NULL because packets can be in transit and xfrm might call xdo_dev_offload_ok() in parallel. All callbacks assume real_dev is set. Example trace: kernel: BUG: unable to handle page fault for address: 0000000000001030 kernel: bond0: (slave eni0np1): making interface the new active one kernel: #PF: supervisor write access in kernel mode kernel: #PF: error_code(0x0002) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: 0002 [#1] PREEMPT SMP kernel: CPU: 4 PID: 2237 Comm: ping Not tainted 6.7.7+ #12 kernel: Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014 kernel: RIP: 0010:nsim_ipsec_offload_ok+0xc/0x20 [netdevsim] kernel: bond0: (slave eni0np1): bond_ipsec_add_sa_all: failed to add SA kernel: Code: e0 0f 0b 48 83 7f 38 00 74 de 0f 0b 48 8b 47 08 48 8b 37 48 8b 78 40 e9 b2 e5 9a d7 66 90 0f 1f 44 00 00 48 8b 86 80 02 00 00 <83> 80 30 10 00 00 01 b8 01 00 00 00 c3 0f 1f 80 00 00 00 00 0f 1f kernel: bond0: (slave eni0np1): making interface the new active one kernel: RSP: 0018:ffffabde81553b98 EFLAGS: 00010246 kernel: bond0: (slave eni0np1): bond_ipsec_add_sa_all: failed to add SA kernel: kernel: RAX: 0000000000000000 RBX: ffff9eb404e74900 RCX: ffff9eb403d97c60 kernel: RDX: ffffffffc090de10 RSI: ffff9eb404e74900 RDI: ffff9eb3c5de9e00 kernel: RBP: ffff9eb3c0a42000 R08: 0000000000000010 R09: 0000000000000014 kernel: R10: 7974203030303030 R11: 3030303030303030 R12: 0000000000000000 kernel: R13: ffff9eb3c5de9e00 R14: ffffabde81553cc8 R15: ffff9eb404c53000 kernel: FS: 00007f2a77a3ad00(0000) GS:ffff9eb43bd00000(0000) knlGS:0000000000000000 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 kernel: CR2: 0000000000001030 CR3: 00000001122ab000 CR4: 0000000000350ef0 kernel: bond0: (slave eni0np1): making interface the new active one kernel: Call Trace: kernel: <TASK> kernel: ? __die+0x1f/0x60 kernel: bond0: (slave eni0np1): bond_ipsec_add_sa_all: failed to add SA kernel: ? page_fault_oops+0x142/0x4c0 kernel: ? do_user_addr_fault+0x65/0x670 kernel: ? kvm_read_and_reset_apf_flags+0x3b/0x50 kernel: bond0: (slave eni0np1): making interface the new active one kernel: ? exc_page_fault+0x7b/0x180 kernel: ? asm_exc_page_fault+0x22/0x30 kernel: ? nsim_bpf_uninit+0x50/0x50 [netdevsim] kernel: bond0: (slave eni0np1): bond_ipsec_add_sa_all: failed to add SA kernel: ? nsim_ipsec_offload_ok+0xc/0x20 [netdevsim] kernel: bond0: (slave eni0np1): making interface the new active one kernel: bond_ipsec_offload_ok+0x7b/0x90 [bonding] kernel: xfrm_output+0x61/0x3b0 kernel: bond0: (slave eni0np1): bond_ipsec_add_sa_all: failed to add SA kernel: ip_push_pending_frames+0x56/0x80 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44987 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: ipv6: prevent UAF in ip6_send_skb() syzbot reported an UAF in ip6_send_skb() [1] After ip6_local_out() has returned, we no longer can safely dereference rt, unless we hold rcu_read_lock(). A similar issue has been fixed in commit a688caa34beb ("ipv6: take rcu lock in rawv6_send_hdrinc()") Another potential issue in ip6_finish_output2() is handled in a separate patch. [1] BUG: KASAN: slab-use-after-free in ip6_send_skb+0x18d/0x230 net/ipv6/ip6_output.c:1964 Read of size 8 at addr ffff88806dde4858 by task syz.1.380/6530 CPU: 1 UID: 0 PID: 6530 Comm: syz.1.380 Not tainted 6.11.0-rc3-syzkaller-00306-gdf6cbc62cc9b #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 ip6_send_skb+0x18d/0x230 net/ipv6/ip6_output.c:1964 rawv6_push_pending_frames+0x75c/0x9e0 net/ipv6/raw.c:588 rawv6_sendmsg+0x19c7/0x23c0 net/ipv6/raw.c:926 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg+0x1a6/0x270 net/socket.c:745 sock_write_iter+0x2dd/0x400 net/socket.c:1160 do_iter_readv_writev+0x60a/0x890 vfs_writev+0x37c/0xbb0 fs/read_write.c:971 do_writev+0x1b1/0x350 fs/read_write.c:1018 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f936bf79e79 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f936cd7f038 EFLAGS: 00000246 ORIG_RAX: 0000000000000014 RAX: ffffffffffffffda RBX: 00007f936c115f80 RCX: 00007f936bf79e79 RDX: 0000000000000001 RSI: 0000000020000040 RDI: 0000000000000004 RBP: 00007f936bfe7916 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f936c115f80 R15: 00007fff2860a7a8 </TASK> Allocated by task 6530: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 unpoison_slab_object mm/kasan/common.c:312 [inline] __kasan_slab_alloc+0x66/0x80 mm/kasan/common.c:338 kasan_slab_alloc include/linux/kasan.h:201 [inline] slab_post_alloc_hook mm/slub.c:3988 [inline] slab_alloc_node mm/slub.c:4037 [inline] kmem_cache_alloc_noprof+0x135/0x2a0 mm/slub.c:4044 dst_alloc+0x12b/0x190 net/core/dst.c:89 ip6_blackhole_route+0x59/0x340 net/ipv6/route.c:2670 make_blackhole net/xfrm/xfrm_policy.c:3120 [inline] xfrm_lookup_route+0xd1/0x1c0 net/xfrm/xfrm_policy.c:3313 ip6_dst_lookup_flow+0x13e/0x180 net/ipv6/ip6_output.c:1257 rawv6_sendmsg+0x1283/0x23c0 net/ipv6/raw.c:898 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg+0x1a6/0x270 net/socket.c:745 ____sys_sendmsg+0x525/0x7d0 net/socket.c:2597 ___sys_sendmsg net/socket.c:2651 [inline] __sys_sendmsg+0x2b0/0x3a0 net/socket.c:2680 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task 45: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579 poison_slab_object+0xe0/0x150 mm/kasan/common.c:240 __kasan_slab_free+0x37/0x60 mm/kasan/common.c:256 kasan_slab_free include/linux/kasan.h:184 [inline] slab_free_hook mm/slub.c:2252 [inline] slab_free mm/slub.c:4473 [inline] kmem_cache_free+0x145/0x350 mm/slub.c:4548 dst_destroy+0x2ac/0x460 net/core/dst.c:124 rcu_do_batch kernel/rcu/tree.c:2569 [inline] rcu_core+0xafd/0x1830 kernel/rcu/tree. ---truncated--- 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44986 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: ipv6: fix possible UAF in ip6_finish_output2() If skb_expand_head() returns NULL, skb has been freed and associated dst/idev could also have been freed. We need to hold rcu_read_lock() to make sure the dst and associated idev are alive. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44985 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: ipv6: prevent possible UAF in ip6_xmit() If skb_expand_head() returns NULL, skb has been freed and the associated dst/idev could also have been freed. We must use rcu_read_lock() to prevent a possible UAF. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44983 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: netfilter: flowtable: validate vlan header Ensure there is sufficient room to access the protocol field of the VLAN header, validate it once before the flowtable lookup. ===================================================== BUG: KMSAN: uninit-value in nf_flow_offload_inet_hook+0x45a/0x5f0 net/netfilter/nf_flow_table_inet.c:32 nf_flow_offload_inet_hook+0x45a/0x5f0 net/netfilter/nf_flow_table_inet.c:32 nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline] nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626 nf_hook_ingress include/linux/netfilter_netdev.h:34 [inline] nf_ingress net/core/dev.c:5440 [inline] 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44982 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: cleanup FB if dpu_format_populate_layout fails If the dpu_format_populate_layout() fails, then FB is prepared, but not cleaned up. This ends up leaking the pin_count on the GEM object and causes a splat during DRM file closure: msm_obj->pin_count WARNING: CPU: 2 PID: 569 at drivers/gpu/drm/msm/msm_gem.c:121 update_lru_locked+0xc4/0xcc [...] Call trace: update_lru_locked+0xc4/0xcc put_pages+0xac/0x100 msm_gem_free_object+0x138/0x180 drm_gem_object_free+0x1c/0x30 drm_gem_object_handle_put_unlocked+0x108/0x10c drm_gem_object_release_handle+0x58/0x70 idr_for_each+0x68/0xec drm_gem_release+0x28/0x40 drm_file_free+0x174/0x234 drm_release+0xb0/0x160 __fput+0xc0/0x2c8 __fput_sync+0x50/0x5c __arm64_sys_close+0x38/0x7c invoke_syscall+0x48/0x118 el0_svc_common.constprop.0+0x40/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x4c/0x120 el0t_64_sync_handler+0x100/0x12c el0t_64_sync+0x190/0x194 irq event stamp: 129818 hardirqs last enabled at (129817): [<ffffa5f6d953fcc0>] console_unlock+0x118/0x124 hardirqs last disabled at (129818): [<ffffa5f6da7dcf04>] el1_dbg+0x24/0x8c softirqs last enabled at (129808): [<ffffa5f6d94afc18>] handle_softirqs+0x4c8/0x4e8 softirqs last disabled at (129785): [<ffffa5f6d94105e4>] __do_softirq+0x14/0x20 Patchwork: https://patchwork.freedesktop.org/patch/600714/ 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44981 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix UBSAN 'subtraction overflow' error in shift_and_mask() UBSAN reports the following 'subtraction overflow' error when booting in a virtual machine on Android: | Internal error: UBSAN: integer subtraction overflow: 00000000f2005515 [#1] PREEMPT SMP | Modules linked in: | CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.10.0-00006-g3cbe9e5abd46-dirty #4 | Hardware name: linux,dummy-virt (DT) | pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) | pc : cancel_delayed_work+0x34/0x44 | lr : cancel_delayed_work+0x2c/0x44 | sp : ffff80008002ba60 | x29: ffff80008002ba60 x28: 0000000000000000 x27: 0000000000000000 | x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000000 | x23: 0000000000000000 x22: 0000000000000000 x21: ffff1f65014cd3c0 | x20: ffffc0e84c9d0da0 x19: ffffc0e84cab3558 x18: ffff800080009058 | x17: 00000000247ee1f8 x16: 00000000247ee1f8 x15: 00000000bdcb279d | x14: 0000000000000001 x13: 0000000000000075 x12: 00000a0000000000 | x11: ffff1f6501499018 x10: 00984901651fffff x9 : ffff5e7cc35af000 | x8 : 0000000000000001 x7 : 3d4d455453595342 x6 : 000000004e514553 | x5 : ffff1f6501499265 x4 : ffff1f650ff60b10 x3 : 0000000000000620 | x2 : ffff80008002ba78 x1 : 0000000000000000 x0 : 0000000000000000 | Call trace: | cancel_delayed_work+0x34/0x44 | deferred_probe_extend_timeout+0x20/0x70 | driver_register+0xa8/0x110 | __platform_driver_register+0x28/0x3c | syscon_init+0x24/0x38 | do_one_initcall+0xe4/0x338 | do_initcall_level+0xac/0x178 | do_initcalls+0x5c/0xa0 | do_basic_setup+0x20/0x30 | kernel_init_freeable+0x8c/0xf8 | kernel_init+0x28/0x1b4 | ret_from_fork+0x10/0x20 | Code: f9000fbf 97fffa2f 39400268 37100048 (d42aa2a0) | ---[ end trace 0000000000000000 ]--- | Kernel panic - not syncing: UBSAN: integer subtraction overflow: Fatal exception This is due to shift_and_mask() using a signed immediate to construct the mask and being called with a shift of 31 (WORK_OFFQ_POOL_SHIFT) so that it ends up decrementing from INT_MIN. Use an unsigned constant '1U' to generate the mask in shift_and_mask(). 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44979 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix missing workqueue destroy in xe_gt_pagefault On driver reload we never free up the memory for the pagefault and access counter workqueues. Add those destroy calls here. (cherry picked from commit 7586fc52b14e0b8edd0d1f8a434e0de2078b7b2b) 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44976 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: ata: pata_macio: Fix DMA table overflow Kolbjørn and Jonáš reported that their 32-bit PowerMacs were crashing in pata-macio since commit 09fe2bfa6b83 ("ata: pata_macio: Fix max_segment_size with PAGE_SIZE == 64K"). For example: kernel BUG at drivers/ata/pata_macio.c:544! Oops: Exception in kernel mode, sig: 5 [#1] BE PAGE_SIZE=4K MMU=Hash SMP NR_CPUS=2 DEBUG_PAGEALLOC PowerMac ... NIP pata_macio_qc_prep+0xf4/0x190 LR pata_macio_qc_prep+0xfc/0x190 Call Trace: 0xc1421660 (unreliable) ata_qc_issue+0x14c/0x2d4 __ata_scsi_queuecmd+0x200/0x53c ata_scsi_queuecmd+0x50/0xe0 scsi_queue_rq+0x788/0xb1c __blk_mq_issue_directly+0x58/0xf4 blk_mq_plug_issue_direct+0x8c/0x1b4 blk_mq_flush_plug_list.part.0+0x584/0x5e0 __blk_flush_plug+0xf8/0x194 __submit_bio+0x1b8/0x2e0 submit_bio_noacct_nocheck+0x230/0x304 btrfs_work_helper+0x200/0x338 process_one_work+0x1a8/0x338 worker_thread+0x364/0x4c0 kthread+0x100/0x104 start_kernel_thread+0x10/0x14 That commit increased max_segment_size to 64KB, with the justification that the SCSI core was already using that size when PAGE_SIZE == 64KB, and that there was existing logic to split over-sized requests. However with a sufficiently large request, the splitting logic causes each sg to be split into two commands in the DMA table, leading to overflow of the DMA table, triggering the BUG_ON(). With default settings the bug doesn't trigger, because the request size is limited by max_sectors_kb == 1280, however max_sectors_kb can be increased, and apparently some distros do that by default using udev rules. Fix the bug for 4KB kernels by reverting to the old max_segment_size. For 64KB kernels the sg_tablesize needs to be halved, to allow for the possibility that each sg will be split into two. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44967 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: drm/mgag200: Bind I2C lifetime to DRM device Managed cleanup with devm_add_action_or_reset() will release the I2C adapter when the underlying Linux device goes away. But the connector still refers to it, so this cleanup leaves behind a stale pointer in struct drm_connector.ddc. Bind the lifetime of the I2C adapter to the connector's lifetime by using DRM's managed release. When the DRM device goes away (after the Linux device) DRM will first clean up the connector and then clean up the I2C adapter. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44970 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink When all the strides in a WQE have been consumed, the WQE is unlinked from the WQ linked list (mlx5_wq_ll_pop()). For SHAMPO, it is possible to receive CQEs with 0 consumed strides for the same WQE even after the WQE is fully consumed and unlinked. This triggers an additional unlink for the same wqe which corrupts the linked list. Fix this scenario by accepting 0 sized consumed strides without unlinking the WQE again. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44964 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: idpf: fix memory leaks and crashes while performing a soft reset The second tagged commit introduced a UAF, as it removed restoring q_vector->vport pointers after reinitializating the structures. This is due to that all queue allocation functions are performed here with the new temporary vport structure and those functions rewrite the backpointers to the vport. Then, this new struct is freed and the pointers start leading to nowhere. But generally speaking, the current logic is very fragile. It claims to be more reliable when the system is low on memory, but in fact, it consumes two times more memory as at the moment of running this function, there are two vports allocated with their queues and vectors. Moreover, it claims to prevent the driver from running into "bad state", but in fact, any error during the rebuild leaves the old vport in the partially allocated state. Finally, if the interface is down when the function is called, it always allocates a new queue set, but when the user decides to enable the interface later on, vport_open() allocates them once again, IOW there's a clear memory leak here. Just don't allocate a new queue set when performing a reset, that solves crashes and memory leaks. Readd the old queue number and reopen the interface on rollback - that solves limbo states when the device is left disabled and/or without HW queues enabled. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44962 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btnxpuart: Shutdown timer and prevent rearming when driver unloading When unload the btnxpuart driver, its associated timer will be deleted. If the timer happens to be modified at this moment, it leads to the kernel call this timer even after the driver unloaded, resulting in kernel panic. Use timer_shutdown_sync() instead of del_timer_sync() to prevent rearming. panic log: Internal error: Oops: 0000000086000007 [#1] PREEMPT SMP Modules linked in: algif_hash algif_skcipher af_alg moal(O) mlan(O) crct10dif_ce polyval_ce polyval_generic snd_soc_imx_card snd_soc_fsl_asoc_card snd_soc_imx_audmux mxc_jpeg_encdec v4l2_jpeg snd_soc_wm8962 snd_soc_fsl_micfil snd_soc_fsl_sai flexcan snd_soc_fsl_utils ap130x rpmsg_ctrl imx_pcm_dma can_dev rpmsg_char pwm_fan fuse [last unloaded: btnxpuart] CPU: 5 PID: 723 Comm: memtester Tainted: G O 6.6.23-lts-next-06207-g4aef2658ac28 #1 Hardware name: NXP i.MX95 19X19 board (DT) pstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : 0xffff80007a2cf464 lr : call_timer_fn.isra.0+0x24/0x80 ... Call trace: 0xffff80007a2cf464 __run_timers+0x234/0x280 run_timer_softirq+0x20/0x40 __do_softirq+0x100/0x26c ____do_softirq+0x10/0x1c call_on_irq_stack+0x24/0x4c do_softirq_own_stack+0x1c/0x2c irq_exit_rcu+0xc0/0xdc el0_interrupt+0x54/0xd8 __el0_irq_handler_common+0x18/0x24 el0t_64_irq_handler+0x10/0x1c el0t_64_irq+0x190/0x194 Code: ???????? ???????? ???????? ???????? (????????) ---[ end trace 0000000000000000 ]--- Kernel panic - not syncing: Oops: Fatal exception in interrupt SMP: stopping secondary CPUs Kernel Offset: disabled CPU features: 0x0,c0000000,40028143,1000721b Memory Limit: none ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]--- 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44963 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: btrfs: do not BUG_ON() when freeing tree block after error When freeing a tree block, at btrfs_free_tree_block(), if we fail to create a delayed reference we don't deal with the error and just do a BUG_ON(). The error most likely to happen is -ENOMEM, and we have a comment mentioning that only -ENOMEM can happen, but that is not true, because in case qgroups are enabled any error returned from btrfs_qgroup_trace_extent_post() (can be -EUCLEAN or anything returned from btrfs_search_slot() for example) can be propagated back to btrfs_free_tree_block(). So stop doing a BUG_ON() and return the error to the callers and make them abort the transaction to prevent leaking space. Syzbot was triggering this, likely due to memory allocation failure injection. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44980 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix opregion leak Being part o the display, ideally the setup and cleanup would be done by display itself. However this is a bigger refactor that needs to be done on both i915 and xe. For now, just fix the leak: unreferenced object 0xffff8881a0300008 (size 192): comm "modprobe", pid 4354, jiffies 4295647021 hex dump (first 32 bytes): 00 00 87 27 81 88 ff ff 18 80 9b 00 00 c9 ff ff ...'............ 18 81 9b 00 00 c9 ff ff 00 00 00 00 00 00 00 00 ................ backtrace (crc 99260e31): [<ffffffff823ce65b>] kmemleak_alloc+0x4b/0x80 [<ffffffff81493be2>] kmalloc_trace_noprof+0x312/0x3d0 [<ffffffffa1345679>] intel_opregion_setup+0x89/0x700 [xe] [<ffffffffa125bfaf>] xe_display_init_noirq+0x2f/0x90 [xe] [<ffffffffa1199ec3>] xe_device_probe+0x7a3/0xbf0 [xe] [<ffffffffa11f3713>] xe_pci_probe+0x333/0x5b0 [xe] [<ffffffff81af6be8>] local_pci_probe+0x48/0xb0 [<ffffffff81af8778>] pci_device_probe+0xc8/0x280 [<ffffffff81d09048>] really_probe+0xf8/0x390 [<ffffffff81d0937a>] __driver_probe_device+0x8a/0x170 [<ffffffff81d09503>] driver_probe_device+0x23/0xb0 [<ffffffff81d097b7>] __driver_attach+0xc7/0x190 [<ffffffff81d0628d>] bus_for_each_dev+0x7d/0xd0 [<ffffffff81d0851e>] driver_attach+0x1e/0x30 [<ffffffff81d07ac7>] bus_add_driver+0x117/0x250 (cherry picked from commit 6f4e43a2f771b737d991142ec4f6d4b7ff31fbb4) 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44965 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: x86/mm: Fix pti_clone_pgtable() alignment assumption Guenter reported dodgy crashes on an i386-nosmp build using GCC-11 that had the form of endless traps until entry stack exhaust and then #DF from the stack guard. It turned out that pti_clone_pgtable() had alignment assumptions on the start address, notably it hard assumes start is PMD aligned. This is true on x86_64, but very much not true on i386. These assumptions can cause the end condition to malfunction, leading to a 'short' clone. Guess what happens when the user mapping has a short copy of the entry text? Use the correct increment form for addr to avoid alignment assumptions. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。
CVE编号: CVE-2024-44973 漏洞描述: In the Linux kernel, the following vulnerability has been resolved: mm, slub: do not call do_slab_free for kfence object In 782f8906f805 the freeing of kfence objects was moved from deep inside do_slab_free to the wrapper functions outside. This is a nice change, but unfortunately it missed one spot in __kmem_cache_free_bulk. This results in a crash like this: BUG skbuff_head_cache (Tainted: G S B E ): Padding overwritten. 0xffff88907fea0f00-0xffff88907fea0fff @offset=3840 slab_err (mm/slub.c:1129) free_to_partial_list (mm/slub.c:? mm/slub.c:4036) slab_pad_check (mm/slub.c:864 mm/slub.c:1290) check_slab (mm/slub.c:?) free_to_partial_list (mm/slub.c:3171 mm/slub.c:4036) kmem_cache_alloc_bulk (mm/slub.c:? mm/slub.c:4495 mm/slub.c:4586 mm/slub.c:4635) napi_build_skb (net/core/skbuff.c:348 net/core/skbuff.c:527 net/core/skbuff.c:549) All the other callers to do_slab_free appear to be ok. Add a kfence_free check in __kmem_cache_free_bulk to avoid the crash. 披露时间: 2024-09-04 CVSS评分: 5.5 解决方案: 建议您更新当前系统或软件至最新版，完成漏洞的修复。