Skip to content

fix(cve): CVE-2026-42616 - ntfscat.c: Fix reading outside the buffer when block size > buffer size.#7

Open
deepin-ci-robot wants to merge 8 commits into
masterfrom
fix-cve/CVE-2026-42616
Open

fix(cve): CVE-2026-42616 - ntfscat.c: Fix reading outside the buffer when block size > buffer size.#7
deepin-ci-robot wants to merge 8 commits into
masterfrom
fix-cve/CVE-2026-42616

Conversation

@deepin-ci-robot

@deepin-ci-robot deepin-ci-robot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

CVE: CVE-2026-42616 (unknown) - ntfscat.c 中当块大小大于缓冲区大小时读取超出缓冲区的问题
Upstream: tuxera/ntfs-3g@dc1b682

Co-authored-by: hudeng hudeng@deepin.org
Generated-By: qwen3.6-35b


CVE: CVE-2026-46572 (unknown) - NTFS-3G 索引条目流不一致漏洞,可能导致拒绝服务
Upstream: GHSA-wx5r-gc7w-9hhc

Co-authored-by: hudeng hudeng@deepin.org
Generated-By: qwen3.6-35b


CVE: CVE-2026-46571 (unknown) - ntfs-3g 的 ntfs_fix_file_name 函数中对 vol->locase 索引使用了原始 16 位代码点且未检查 vol->upcase_len 边界。截断的 使表短于 65536 项,导致文件名字符 >= upcase_len 时读取越界,通过符号链接目标向用户空间泄漏 2 字节堆内存。
Upstream: tuxera/ntfs-3g@b912272

Co-authored-by: hudeng hudeng@deepin.org
Generated-By: qwen3.6-35b


CVE: CVE-2026-42617 (unknown) - CVE-2026-42617 ntfs-3g 安全漏洞修复
Upstream: GHSA-jv65-qqf7-f692

Co-authored-by: hudeng hudeng@deepin.org
Generated-By: qwen3.6-35b


CVE: CVE-2026-56135 (unknown) - ACLs: Fix inherited ACL buffer sizing.
Upstream: tuxera/ntfs-3g@289ebcf

Co-authored-by: hudeng hudeng@deepin.org
Generated-By: qwen3.6-35b

deepin-ci-robot and others added 3 commits July 17, 2026 16:41
…ession bounds checks.

CVE: CVE-2026-42618 (unknown) - ntfs-3g LZNT1 sub-block decompression bounds check vulnerability allowing out-of-bounds write
Upstream: tuxera/ntfs-3g@6aa66d9

Co-authored-by: hudeng <hudeng@deepin.org>
Generated-By: qwen3.6-35b
…when block size > buffer size.

CVE: CVE-2026-42616 (unknown) - ntfs-3g 中 ntfscat.c 的缓冲区溢出漏洞,当块大小大于缓冲区大小时会导致读取超出分配的缓冲区。
Upstream: tuxera/ntfs-3g@dc1b682

Co-authored-by: hudeng <hudeng@deepin.org>
Generated-By: qwen3.6-35b
…when block size > buffer size.

CVE: CVE-2026-42616 (unknown) - ntfscat.c 中当块大小大于缓冲区大小时读取超出缓冲区的问题
Upstream: tuxera/ntfs-3g@dc1b682

Co-authored-by: hudeng <hudeng@deepin.org>
Generated-By: qwen3.6-35b
@deepin-ci-robot

Copy link
Copy Markdown
Contributor Author

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign liujianqiang-niu for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@github-actions

github-actions Bot commented Jul 17, 2026

Copy link
Copy Markdown

TAG Bot

TAG: 1%2022.10.3-5+deb13u1deepin8
EXISTED: no
DISTRIBUTION: unstable

@deepin-ci-robot

Copy link
Copy Markdown
Contributor Author

/hold
因为该quilt包的上游版本号变更,详情见: deepin-community/infra-settings#134

deepin-ci-robot and others added 5 commits July 21, 2026 10:52
CVE: CVE-2026-46572 (unknown) - NTFS-3G 索引条目流不一致漏洞,可能导致拒绝服务
Upstream: GHSA-wx5r-gc7w-9hhc

Co-authored-by: hudeng <hudeng@deepin.org>
Generated-By: qwen3.6-35b
…fs_fix_file_name.

CVE: CVE-2026-46571 (unknown) - ntfs-3g 的 ntfs_fix_file_name 函数中对 vol->locase 索引使用了原始 16 位代码点且未检查 vol->upcase_len 边界。截断的  使表短于 65536 项,导致文件名字符 >= upcase_len 时读取越界,通过符号链接目标向用户空间泄漏 2 字节堆内存。
Upstream: tuxera/ntfs-3g@b912272

Co-authored-by: hudeng <hudeng@deepin.org>
Generated-By: qwen3.6-35b


CVE: CVE-2026-42617 (unknown) - CVE-2026-42617 ntfs-3g 安全漏洞修复
Upstream: GHSA-jv65-qqf7-f692

Co-authored-by: hudeng <hudeng@deepin.org>
Generated-By: qwen3.6-35b
CVE: CVE-2026-56135 (unknown) - ACLs: Fix inherited ACL buffer sizing.
Upstream: tuxera/ntfs-3g@289ebcf

Co-authored-by: hudeng <hudeng@deepin.org>
Generated-By: qwen3.6-35b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants