idx int64 | project string | commit_id string | project_url string | commit_url string | commit_message string | target int64 | func string | func_hash float64 | file_name string | file_hash float64 | cwe list | cve string | cve_desc string | nvd_url string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
36,808 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da3_node_read(
struct xfs_trans *tp,
struct xfs_inode *dp,
xfs_dablk_t bno,
xfs_daddr_t mappedbno,
struct xfs_buf **bpp,
int which_fork)
{
int err;
err = xfs_da_read_buf(tp, dp, bno, mappedbno, bpp,
which_fork, &xfs_da3_node_buf_ops);
if (!err && tp) {
struct xfs_da_blkinfo *info = (*bpp)->b... | 277,993,058,678,718,260,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,809 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da3_node_read_verify(
struct xfs_buf *bp)
{
struct xfs_mount *mp = bp->b_target->bt_mount;
struct xfs_da_blkinfo *info = bp->b_addr;
switch (be16_to_cpu(info->magic)) {
case XFS_DA3_NODE_MAGIC:
if (!xfs_verify_cksum(bp->b_addr, BBTOB(bp->b_length),
XFS_DA3_NODE_CRC_OFF))
break;
/* fall ... | 248,270,336,832,939,400,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,810 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da3_node_remove(
struct xfs_da_state *state,
struct xfs_da_state_blk *drop_blk)
{
struct xfs_da_intnode *node;
struct xfs_da3_icnode_hdr nodehdr;
struct xfs_da_node_entry *btree;
int index;
int tmp;
struct xfs_inode *dp = state->args->dp;
trace_xfs_da_node_remove(state->args);
node = drop_blk->bp->b... | 95,599,176,678,464,870,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,811 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da3_node_split(
struct xfs_da_state *state,
struct xfs_da_state_blk *oldblk,
struct xfs_da_state_blk *newblk,
struct xfs_da_state_blk *addblk,
int treelevel,
int *result)
{
struct xfs_da_intnode *node;
struct xfs_da3_icnode_hdr nodehdr;
xfs_dablk_t blkno;
int newcount;
int error;
int useextra... | 47,468,032,056,909,570,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,812 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da3_node_toosmall(
struct xfs_da_state *state,
int *action)
{
struct xfs_da_intnode *node;
struct xfs_da_state_blk *blk;
struct xfs_da_blkinfo *info;
xfs_dablk_t blkno;
struct xfs_buf *bp;
struct xfs_da3_icnode_hdr nodehdr;
int count;
int forward;
int error;
int retval;
int i;
struct xfs... | 19,310,961,927,454,070,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,813 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da3_node_unbalance(
struct xfs_da_state *state,
struct xfs_da_state_blk *drop_blk,
struct xfs_da_state_blk *save_blk)
{
struct xfs_da_intnode *drop_node;
struct xfs_da_intnode *save_node;
struct xfs_da_node_entry *drop_btree;
struct xfs_da_node_entry *save_btree;
struct xfs_da3_icnode_hdr drop_hdr;
struct ... | 270,696,697,852,335,600,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,814 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da3_node_verify(
struct xfs_buf *bp)
{
struct xfs_mount *mp = bp->b_target->bt_mount;
struct xfs_da_intnode *hdr = bp->b_addr;
struct xfs_da3_icnode_hdr ichdr;
const struct xfs_dir_ops *ops;
ops = xfs_dir_get_ops(mp, NULL);
ops->node_hdr_from_disk(&ichdr, hdr);
if (xfs_sb_version_hascrc(&mp->m_sb)) {
... | 87,519,873,158,516,020,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,815 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da3_node_write_verify(
struct xfs_buf *bp)
{
struct xfs_mount *mp = bp->b_target->bt_mount;
struct xfs_buf_log_item *bip = bp->b_fspriv;
struct xfs_da3_node_hdr *hdr3 = bp->b_addr;
if (!xfs_da3_node_verify(bp)) {
XFS_CORRUPTION_ERROR(__func__, XFS_ERRLEVEL_LOW, mp, bp->b_addr);
xfs_buf_ioerror(bp, EFSCORR... | 334,346,043,413,777,420,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,816 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da3_path_shift(
struct xfs_da_state *state,
struct xfs_da_state_path *path,
int forward,
int release,
int *result)
{
struct xfs_da_state_blk *blk;
struct xfs_da_blkinfo *info;
struct xfs_da_intnode *node;
struct xfs_da_args *args;
struct xfs_da_node_entry *btree;
struct xfs_da3_icnode_hdr nodehdr;
... | 191,507,172,410,244,180,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,817 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da3_root_join(
struct xfs_da_state *state,
struct xfs_da_state_blk *root_blk)
{
struct xfs_da_intnode *oldroot;
struct xfs_da_args *args;
xfs_dablk_t child;
struct xfs_buf *bp;
struct xfs_da3_icnode_hdr oldroothdr;
struct xfs_da_node_entry *btree;
int error;
struct xfs_inode *dp = state->args->dp;
t... | 245,153,016,946,709,700,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,818 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da3_root_split(
struct xfs_da_state *state,
struct xfs_da_state_blk *blk1,
struct xfs_da_state_blk *blk2)
{
struct xfs_da_intnode *node;
struct xfs_da_intnode *oldroot;
struct xfs_da_node_entry *btree;
struct xfs_da3_icnode_hdr nodehdr;
struct xfs_da_args *args;
struct xfs_buf *bp;
struct xfs_inode *dp;
... | 132,073,406,680,022,980,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,819 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da3_split(
struct xfs_da_state *state)
{
struct xfs_da_state_blk *oldblk;
struct xfs_da_state_blk *newblk;
struct xfs_da_state_blk *addblk;
struct xfs_da_intnode *node;
struct xfs_buf *bp;
int max;
int action = 0;
int error;
int i;
trace_xfs_da_split(state->args);
/*
* Walk back up the tree... | 155,398,971,679,030,040,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,820 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da3_swap_lastblock(
struct xfs_da_args *args,
xfs_dablk_t *dead_blknop,
struct xfs_buf **dead_bufp)
{
struct xfs_da_blkinfo *dead_info;
struct xfs_da_blkinfo *sib_info;
struct xfs_da_intnode *par_node;
struct xfs_da_intnode *dead_node;
struct xfs_dir2_leaf *dead_leaf2;
struct xfs_da_node_entry *btree;
s... | 237,868,719,887,769,670,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,821 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da_blkinfo_onlychild_validate(struct xfs_da_blkinfo *blkinfo, __u16 level)
{
__be16 magic = blkinfo->magic;
if (level == 1) {
ASSERT(magic == cpu_to_be16(XFS_DIR2_LEAFN_MAGIC) ||
magic == cpu_to_be16(XFS_DIR3_LEAFN_MAGIC) ||
magic == cpu_to_be16(XFS_ATTR_LEAF_MAGIC) ||
magic == cpu_t... | 205,007,528,099,217,030,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,822 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da_compname(
struct xfs_da_args *args,
const unsigned char *name,
int len)
{
return (args->namelen == len && memcmp(args->name, name, len) == 0) ?
XFS_CMP_EXACT : XFS_CMP_DIFFERENT;
}
| 180,420,838,373,507,560,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,823 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da_get_buf(
struct xfs_trans *trans,
struct xfs_inode *dp,
xfs_dablk_t bno,
xfs_daddr_t mappedbno,
struct xfs_buf **bpp,
int whichfork)
{
struct xfs_buf *bp;
struct xfs_buf_map map;
struct xfs_buf_map *mapp;
int nmap;
int error;
*bpp = NULL;
mapp = ↦
nmap = 1;
error = xfs_dabuf_map(tra... | 38,688,143,837,992,520,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,824 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da_grow_inode(
struct xfs_da_args *args,
xfs_dablk_t *new_blkno)
{
xfs_fileoff_t bno;
int count;
int error;
trace_xfs_da_grow_inode(args);
if (args->whichfork == XFS_DATA_FORK) {
bno = args->dp->i_mount->m_dirleafblk;
count = args->dp->i_mount->m_dirblkfsbs;
} else {
bno = 0;
count = 1;
}
... | 301,840,133,505,341,300,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,825 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da_grow_inode_int(
struct xfs_da_args *args,
xfs_fileoff_t *bno,
int count)
{
struct xfs_trans *tp = args->trans;
struct xfs_inode *dp = args->dp;
int w = args->whichfork;
xfs_drfsbno_t nblks = dp->i_d.di_nblocks;
struct xfs_bmbt_irec map, *mapp;
int nmap, error, got, i, mapi;
/*
* Find a spot ... | 130,681,275,658,985,700,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,826 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da_map_covers_blocks(
int nmap,
xfs_bmbt_irec_t *mapp,
xfs_dablk_t bno,
int count)
{
int i;
xfs_fileoff_t off;
for (i = 0, off = bno; i < nmap; i++) {
if (mapp[i].br_startblock == HOLESTARTBLOCK ||
mapp[i].br_startblock == DELAYSTARTBLOCK) {
return 0;
}
if (off != mapp[i].br_startoff) {
... | 158,184,557,494,368,200,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,827 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da_read_buf(
struct xfs_trans *trans,
struct xfs_inode *dp,
xfs_dablk_t bno,
xfs_daddr_t mappedbno,
struct xfs_buf **bpp,
int whichfork,
const struct xfs_buf_ops *ops)
{
struct xfs_buf *bp;
struct xfs_buf_map map;
struct xfs_buf_map *mapp;
int nmap;
int error;
*bpp = NULL;
mapp = ↦
nma... | 140,481,603,941,663,070,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,828 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da_reada_buf(
struct xfs_trans *trans,
struct xfs_inode *dp,
xfs_dablk_t bno,
xfs_daddr_t mappedbno,
int whichfork,
const struct xfs_buf_ops *ops)
{
struct xfs_buf_map map;
struct xfs_buf_map *mapp;
int nmap;
int error;
mapp = ↦
nmap = 1;
error = xfs_dabuf_map(trans, dp, bno, mappedbno, wh... | 307,900,250,574,928,700,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,829 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da_shrink_inode(
xfs_da_args_t *args,
xfs_dablk_t dead_blkno,
struct xfs_buf *dead_buf)
{
xfs_inode_t *dp;
int done, error, w, count;
xfs_trans_t *tp;
xfs_mount_t *mp;
trace_xfs_da_shrink_inode(args);
dp = args->dp;
w = args->whichfork;
tp = args->trans;
mp = dp->i_mount;
if (w == XFS_DATA_FORK)
co... | 57,599,740,904,319,160,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,830 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da_state_alloc(void)
{
return kmem_zone_zalloc(xfs_da_state_zone, KM_NOFS);
}
| 7,746,856,679,617,136,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,831 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da_state_free(xfs_da_state_t *state)
{
xfs_da_state_kill_altpath(state);
#ifdef DEBUG
memset((char *)state, 0, sizeof(*state));
#endif /* DEBUG */
kmem_zone_free(xfs_da_state_zone, state);
}
| 261,110,648,550,279,240,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,832 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da_state_kill_altpath(xfs_da_state_t *state)
{
int i;
for (i = 0; i < state->altpath.active; i++)
state->altpath.blk[i].bp = NULL;
state->altpath.active = 0;
}
| 132,358,307,714,416,330,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,833 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_dabuf_map(
struct xfs_trans *trans,
struct xfs_inode *dp,
xfs_dablk_t bno,
xfs_daddr_t mappedbno,
int whichfork,
struct xfs_buf_map **map,
int *nmaps)
{
struct xfs_mount *mp = dp->i_mount;
int nfsb;
int error = 0;
struct xfs_bmbt_irec irec;
struct xfs_bmbt_irec *irecs = &irec;
int nirecs;
... | 10,429,484,983,901,630,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,834 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_default_hashname(
struct xfs_name *name)
{
return xfs_da_hashname(name->name, name->len);
}
| 164,961,663,218,392,600,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
36,835 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_QFS_attr(const unsigned int xid, struct cifs_tcon *tcon,
u64 persistent_fid, u64 volatile_fid, int level)
{
struct smb2_query_info_rsp *rsp = NULL;
struct kvec iov;
int rc = 0;
int resp_buftype, max_len, min_len;
struct cifs_ses *ses = tcon->ses;
unsigned int rsp_len, offset;
if (level == FS_DEVICE_... | 32,465,118,015,756,397,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,836 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_QFS_info(const unsigned int xid, struct cifs_tcon *tcon,
u64 persistent_fid, u64 volatile_fid, struct kstatfs *fsdata)
{
struct smb2_query_info_rsp *rsp = NULL;
struct kvec iov;
int rc = 0;
int resp_buftype;
struct cifs_ses *ses = tcon->ses;
struct smb2_fs_full_size_info *info = NULL;
rc = build_qfs... | 147,850,633,250,791,910,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,837 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_close(const unsigned int xid, struct cifs_tcon *tcon,
u64 persistent_fid, u64 volatile_fid)
{
struct smb2_close_req *req;
struct smb2_close_rsp *rsp;
struct TCP_Server_Info *server;
struct cifs_ses *ses = tcon->ses;
struct kvec iov[1];
int resp_buftype;
int rc = 0;
cifs_dbg(FYI, "Close\n");
if (ses ... | 77,315,426,941,755,630,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,838 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_echo(struct TCP_Server_Info *server)
{
struct smb2_echo_req *req;
int rc = 0;
struct kvec iov;
struct smb_rqst rqst = { .rq_iov = &iov,
.rq_nvec = 1 };
cifs_dbg(FYI, "In echo request\n");
rc = small_smb2_init(SMB2_ECHO, NULL, (void **)&req);
if (rc)
return rc;
req->hdr.CreditRequest = cpu_to_le16... | 203,254,842,323,390,130,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,839 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_flush(const unsigned int xid, struct cifs_tcon *tcon, u64 persistent_fid,
u64 volatile_fid)
{
struct smb2_flush_req *req;
struct TCP_Server_Info *server;
struct cifs_ses *ses = tcon->ses;
struct kvec iov[1];
int resp_buftype;
int rc = 0;
cifs_dbg(FYI, "Flush\n");
if (ses && (ses->server))
server = ... | 127,822,803,225,850,630,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,840 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_ioctl(const unsigned int xid, struct cifs_tcon *tcon, u64 persistent_fid,
u64 volatile_fid, u32 opcode, bool is_fsctl, char *in_data,
u32 indatalen, char **out_data, u32 *plen /* returned data len */)
{
struct smb2_ioctl_req *req;
struct smb2_ioctl_rsp *rsp;
struct TCP_Server_Info *server;
struct cifs_... | 244,409,493,057,389,040,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,841 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_lock(const unsigned int xid, struct cifs_tcon *tcon,
const __u64 persist_fid, const __u64 volatile_fid, const __u32 pid,
const __u64 length, const __u64 offset, const __u32 lock_flags,
const bool wait)
{
struct smb2_lock_element lock;
lock.Offset = cpu_to_le64(offset);
lock.Length = cpu_to_le64(length... | 89,356,993,068,675,300,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,842 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_logoff(const unsigned int xid, struct cifs_ses *ses)
{
struct smb2_logoff_req *req; /* response is also trivial struct */
int rc = 0;
struct TCP_Server_Info *server;
cifs_dbg(FYI, "disconnect session %p\n", ses);
if (ses && (ses->server))
server = ses->server;
else
return -EIO;
/* no need to send SMB... | 94,808,826,421,818,700,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,843 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_negotiate(const unsigned int xid, struct cifs_ses *ses)
{
struct smb2_negotiate_req *req;
struct smb2_negotiate_rsp *rsp;
struct kvec iov[1];
int rc = 0;
int resp_buftype;
struct TCP_Server_Info *server = ses->server;
int blob_offset, blob_length;
char *security_blob;
int flags = CIFS_NEG_OP;
cifs_dbg(F... | 51,271,817,395,171,600,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,844 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_open(const unsigned int xid, struct cifs_open_parms *oparms, __le16 *path,
__u8 *oplock, struct smb2_file_all_info *buf,
struct smb2_err_rsp **err_buf)
{
struct smb2_create_req *req;
struct smb2_create_rsp *rsp;
struct TCP_Server_Info *server;
struct cifs_tcon *tcon = oparms->tcon;
struct cifs_ses *ses ... | 100,493,070,189,137,870,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,845 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_oplock_break(const unsigned int xid, struct cifs_tcon *tcon,
const u64 persistent_fid, const u64 volatile_fid,
__u8 oplock_level)
{
int rc;
struct smb2_oplock_break *req = NULL;
cifs_dbg(FYI, "SMB2_oplock_break\n");
rc = small_smb2_init(SMB2_OPLOCK_BREAK, tcon, (void **) &req);
if (rc)
return rc;
... | 231,887,109,652,177,770,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,846 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_query_info(const unsigned int xid, struct cifs_tcon *tcon,
u64 persistent_fid, u64 volatile_fid,
struct smb2_file_all_info *data)
{
return query_info(xid, tcon, persistent_fid, volatile_fid,
FILE_ALL_INFORMATION,
sizeof(struct smb2_file_all_info) + MAX_NAME * 2,
sizeof(struct smb2_file_all_info... | 220,899,631,866,519,200,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,847 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_read(const unsigned int xid, struct cifs_io_parms *io_parms,
unsigned int *nbytes, char **buf, int *buf_type)
{
int resp_buftype, rc = -EACCES;
struct smb2_read_rsp *rsp = NULL;
struct kvec iov[1];
*nbytes = 0;
rc = smb2_new_read_req(iov, io_parms, 0, 0);
if (rc)
return rc;
rc = SendReceive2(xid, io_... | 67,431,837,919,528,140,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,848 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_rename(const unsigned int xid, struct cifs_tcon *tcon,
u64 persistent_fid, u64 volatile_fid, __le16 *target_file)
{
struct smb2_file_rename_info info;
void **data;
unsigned int size[2];
int rc;
int len = (2 * UniStrnlen((wchar_t *)target_file, PATH_MAX));
data = kmalloc(sizeof(void *) * 2, GFP_KERNEL);... | 266,410,655,327,603,850,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,849 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_sess_setup(const unsigned int xid, struct cifs_ses *ses,
const struct nls_table *nls_cp)
{
struct smb2_sess_setup_req *req;
struct smb2_sess_setup_rsp *rsp = NULL;
struct kvec iov[2];
int rc = 0;
int resp_buftype;
__le32 phase = NtLmNegotiate; /* NTLMSSP, if needed, is multistage */
struct TCP_Server_Info... | 148,162,995,107,558,650,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,850 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_set_compression(const unsigned int xid, struct cifs_tcon *tcon,
u64 persistent_fid, u64 volatile_fid)
{
int rc;
struct compress_ioctl fsctl_input;
char *ret_data = NULL;
fsctl_input.CompressionState =
__constant_cpu_to_le16(COMPRESSION_FORMAT_DEFAULT);
rc = SMB2_ioctl(xid, tcon, persistent_fid, v... | 25,509,873,422,239,250,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,851 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_set_info(const unsigned int xid, struct cifs_tcon *tcon,
u64 persistent_fid, u64 volatile_fid, FILE_BASIC_INFO *buf)
{
unsigned int size;
size = sizeof(FILE_BASIC_INFO);
return send_set_info(xid, tcon, persistent_fid, volatile_fid,
current->tgid, FILE_BASIC_INFORMATION, 1,
(void **)&buf, ... | 12,354,591,018,332,815,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,852 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_tdis(const unsigned int xid, struct cifs_tcon *tcon)
{
struct smb2_tree_disconnect_req *req; /* response is trivial */
int rc = 0;
struct TCP_Server_Info *server;
struct cifs_ses *ses = tcon->ses;
cifs_dbg(FYI, "Tree Disconnect\n");
if (ses && (ses->server))
server = ses->server;
else
return -EIO;
i... | 262,101,708,566,241,840,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,853 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_write(const unsigned int xid, struct cifs_io_parms *io_parms,
unsigned int *nbytes, struct kvec *iov, int n_vec)
{
int rc = 0;
struct smb2_write_req *req = NULL;
struct smb2_write_rsp *rsp = NULL;
int resp_buftype;
*nbytes = 0;
if (n_vec < 1)
return rc;
rc = small_smb2_init(SMB2_WRITE, io_parms->tco... | 6,139,157,861,978,873,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,854 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | add_durable_context(struct kvec *iov, unsigned int *num_iovec,
struct cifs_open_parms *oparms)
{
struct smb2_create_req *req = iov[0].iov_base;
unsigned int num = *num_iovec;
if (oparms->reconnect) {
iov[num].iov_base = create_reconnect_durable_buf(oparms->fid);
/* indicate that we don't need to relock th... | 11,469,506,910,472,072,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,855 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | add_lease_context(struct TCP_Server_Info *server, struct kvec *iov,
unsigned int *num_iovec, __u8 *oplock)
{
struct smb2_create_req *req = iov[0].iov_base;
unsigned int num = *num_iovec;
iov[num].iov_base = server->ops->create_lease_buf(oplock+1, *oplock);
if (iov[num].iov_base == NULL)
return -ENOMEM;
iov[... | 120,492,879,911,629,390,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,856 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | build_qfs_info_req(struct kvec *iov, struct cifs_tcon *tcon, int level,
int outbuf_len, u64 persistent_fid, u64 volatile_fid)
{
int rc;
struct smb2_query_info_req *req;
cifs_dbg(FYI, "Query FSInfo level %d\n", level);
if ((tcon->ses == NULL) || (tcon->ses->server == NULL))
return -EIO;
rc = small_smb2_in... | 131,776,026,867,839,340,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,857 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | static inline void cifs_stats_fail_inc(struct cifs_tcon *tcon, uint16_t code)
{
cifs_stats_inc(&tcon->stats.smb2_stats.smb2_com_failed[code]);
}
| 57,143,255,476,021,400,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,858 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | copy_fs_info_to_kstatfs(struct smb2_fs_full_size_info *pfs_inf,
struct kstatfs *kst)
{
kst->f_bsize = le32_to_cpu(pfs_inf->BytesPerSector) *
le32_to_cpu(pfs_inf->SectorsPerAllocationUnit);
kst->f_blocks = le64_to_cpu(pfs_inf->TotalAllocationUnits);
kst->f_bfree = le64_to_cpu(pfs_inf->ActualAvailableAllocati... | 57,797,350,807,305,790,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,859 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | create_durable_buf(void)
{
struct create_durable *buf;
buf = kzalloc(sizeof(struct create_durable), GFP_KERNEL);
if (!buf)
return NULL;
buf->ccontext.DataOffset = cpu_to_le16(offsetof
(struct create_durable, Data));
buf->ccontext.DataLength = cpu_to_le32(16);
buf->ccontext.NameOffset = cpu_to_le16(offset... | 188,965,687,582,477,400,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,860 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | static inline void init_copy_chunk_defaults(struct cifs_tcon *tcon)
{
tcon->max_chunks = 256;
tcon->max_bytes_chunk = 1048576;
tcon->max_bytes_copy = 16777216;
}
| 87,485,426,231,198,950,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,861 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | num_entries(char *bufstart, char *end_of_buf, char **lastentry, size_t size)
{
int len;
unsigned int entrycount = 0;
unsigned int next_offset = 0;
FILE_DIRECTORY_INFO *entryptr;
if (bufstart == NULL)
return 0;
entryptr = (FILE_DIRECTORY_INFO *)bufstart;
while (1) {
entryptr = (FILE_DIRECTORY_INFO *)
... | 144,523,868,668,404,160,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,862 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | parse_lease_state(struct TCP_Server_Info *server, struct smb2_create_rsp *rsp,
unsigned int *epoch)
{
char *data_offset;
struct create_context *cc;
unsigned int next = 0;
char *name;
data_offset = (char *)rsp + 4 + le32_to_cpu(rsp->CreateContextsOffset);
cc = (struct create_context *)data_offset;
do {
cc ... | 210,622,164,892,064,920,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,863 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | send_set_info(const unsigned int xid, struct cifs_tcon *tcon,
u64 persistent_fid, u64 volatile_fid, u32 pid, int info_class,
unsigned int num, void **data, unsigned int *size)
{
struct smb2_set_info_req *req;
struct smb2_set_info_rsp *rsp = NULL;
struct kvec *iov;
int rc = 0;
int resp_buftype;
uns... | 44,908,150,681,163,810,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,864 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | smb2_async_readv(struct cifs_readdata *rdata)
{
int rc, flags = 0;
struct smb2_hdr *buf;
struct cifs_io_parms io_parms;
struct smb_rqst rqst = { .rq_iov = &rdata->iov,
.rq_nvec = 1 };
struct TCP_Server_Info *server;
cifs_dbg(FYI, "%s: offset=%llu bytes=%u\n",
__func__, rdata->offset, rdata->bytes);
io_... | 320,027,262,491,284,150,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,865 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | smb2_async_writev(struct cifs_writedata *wdata,
void (*release)(struct kref *kref))
{
int rc = -EACCES, flags = 0;
struct smb2_write_req *req = NULL;
struct cifs_tcon *tcon = tlink_tcon(wdata->cfile->tlink);
struct TCP_Server_Info *server = tcon->ses->server;
struct kvec iov;
struct smb_rqst rqst;
rc = smal... | 232,316,655,686,923,500,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,866 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | smb2_echo_callback(struct mid_q_entry *mid)
{
struct TCP_Server_Info *server = mid->callback_data;
struct smb2_echo_rsp *smb2 = (struct smb2_echo_rsp *)mid->resp_buf;
unsigned int credits_received = 1;
if (mid->mid_state == MID_RESPONSE_RECEIVED)
credits_received = le16_to_cpu(smb2->hdr.CreditRequest);
DeleteM... | 45,588,918,560,505,200,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,867 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | smb2_hdr_assemble(struct smb2_hdr *hdr, __le16 smb2_cmd /* command */ ,
const struct cifs_tcon *tcon)
{
struct smb2_pdu *pdu = (struct smb2_pdu *)hdr;
char *temp = (char *)hdr;
/* lookup word count ie StructureSize from table */
__u16 parmsize = smb2_req_struct_sizes[le16_to_cpu(smb2_cmd)];
/*
* smaller tha... | 88,424,185,748,536,600,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,868 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | smb2_lockv(const unsigned int xid, struct cifs_tcon *tcon,
const __u64 persist_fid, const __u64 volatile_fid, const __u32 pid,
const __u32 num_lock, struct smb2_lock_element *buf)
{
int rc = 0;
struct smb2_lock_req *req = NULL;
struct kvec iov[2];
int resp_buf_type;
unsigned int count;
cifs_dbg(FYI, "smb... | 102,781,308,044,390,060,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,869 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | smb2_new_read_req(struct kvec *iov, struct cifs_io_parms *io_parms,
unsigned int remaining_bytes, int request_type)
{
int rc = -EACCES;
struct smb2_read_req *req = NULL;
rc = small_smb2_init(SMB2_READ, io_parms->tcon, (void **) &req);
if (rc)
return rc;
if (io_parms->tcon->ses->server == NULL)
return -ECO... | 154,888,183,630,626,410,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,870 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | smb2_reconnect(__le16 smb2_command, struct cifs_tcon *tcon)
{
int rc = 0;
struct nls_table *nls_codepage;
struct cifs_ses *ses;
struct TCP_Server_Info *server;
/*
* SMB2s NegProt, SessSetup, Logoff do not have tcon yet so
* check for tcp and smb session status done differently
* for those three - in the cal... | 86,327,462,526,166,200,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,871 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | int smb3_validate_negotiate(const unsigned int xid, struct cifs_tcon *tcon)
{
int rc = 0;
struct validate_negotiate_info_req vneg_inbuf;
struct validate_negotiate_info_rsp *pneg_rsp;
u32 rsplen;
cifs_dbg(FYI, "validate negotiate\n");
/*
* validation ioctl must be signed, so no point sending this if we
* can... | 5,844,024,824,297,132,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,872 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | validate_and_copy_buf(unsigned int offset, unsigned int buffer_length,
struct smb2_hdr *hdr, unsigned int minbufsize,
char *data)
{
char *begin_of_buf = 4 /* RFC1001 len field */ + offset + (char *)hdr;
int rc;
if (!data)
return -EINVAL;
rc = validate_buf(offset, buffer_length, hdr, minbufsize)... | 159,232,309,735,729,990,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,873 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | validate_buf(unsigned int offset, unsigned int buffer_length,
struct smb2_hdr *hdr, unsigned int min_buf_size)
{
unsigned int smb_len = be32_to_cpu(hdr->smb2_buf_length);
char *end_of_smb = smb_len + 4 /* RFC1001 length field */ + (char *)hdr;
char *begin_of_buf = 4 /* RFC1001 len field */ + offset + (char *)... | 193,633,177,114,411,060,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
36,891 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static void __udf_clear_extent_cache(struct inode *inode)
{
struct udf_inode_info *iinfo = UDF_I(inode);
if (iinfo->cached_extent.lstart != -1) {
brelse(iinfo->cached_extent.epos.bh);
iinfo->cached_extent.lstart = -1;
}
}
| 106,589,119,027,281,570,000,000,000,000,000,000,000 | inode.c | 299,509,065,903,875,730,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,892 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | int8_t inode_bmap(struct inode *inode, sector_t block,
struct extent_position *pos, struct kernel_lb_addr *eloc,
uint32_t *elen, sector_t *offset)
{
unsigned char blocksize_bits = inode->i_sb->s_blocksize_bits;
loff_t lbcount = 0, bcount =
(loff_t) block << blocksize_bits;
int8_t etype;
struct udf_inod... | 247,012,468,147,981,200,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,893 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static sector_t inode_getblk(struct inode *inode, sector_t block,
int *err, int *new)
{
struct kernel_long_ad laarr[EXTENT_MERGE_SIZE];
struct extent_position prev_epos, cur_epos, next_epos;
int count = 0, startnum = 0, endnum = 0;
uint32_t elen = 0, tmpelen;
struct kernel_lb_addr eloc, tmpeloc;
int c = 1... | 248,080,846,693,602,800,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,894 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static int udf_alloc_i_data(struct inode *inode, size_t size)
{
struct udf_inode_info *iinfo = UDF_I(inode);
iinfo->i_ext.i_data = kmalloc(size, GFP_KERNEL);
if (!iinfo->i_ext.i_data) {
udf_err(inode->i_sb, "(ino %ld) no free memory\n",
inode->i_ino);
return -ENOMEM;
}
return 0;
}
| 160,566,670,227,847,430,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,895 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static sector_t udf_bmap(struct address_space *mapping, sector_t block)
{
return generic_block_bmap(mapping, block, udf_get_block);
}
| 261,734,541,707,027,000,000,000,000,000,000,000,000 | inode.c | 299,509,065,903,875,730,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,896 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | struct buffer_head *udf_bread(struct inode *inode, int block,
int create, int *err)
{
struct buffer_head *bh = NULL;
bh = udf_getblk(inode, block, create, err);
if (!bh)
return NULL;
if (buffer_uptodate(bh))
return bh;
ll_rw_block(READ, 1, &bh);
wait_on_buffer(bh);
if (buffer_uptodate(bh))
ret... | 63,134,065,950,378,910,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,897 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static void udf_clear_extent_cache(struct inode *inode)
{
struct udf_inode_info *iinfo = UDF_I(inode);
spin_lock(&iinfo->i_extent_cache_lock);
__udf_clear_extent_cache(inode);
spin_unlock(&iinfo->i_extent_cache_lock);
}
| 103,746,734,399,438,400,000,000,000,000,000,000,000 | inode.c | 299,509,065,903,875,730,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,898 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static umode_t udf_convert_permissions(struct fileEntry *fe)
{
umode_t mode;
uint32_t permissions;
uint32_t flags;
permissions = le32_to_cpu(fe->permissions);
flags = le16_to_cpu(fe->icbTag.flags);
mode = ((permissions) & S_IRWXO) |
((permissions >> 2) & S_IRWXG) |
((permissions >> 4) & S_IRWXU) |
((flags... | 125,913,370,358,697,430,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,899 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | int8_t udf_current_aext(struct inode *inode, struct extent_position *epos,
struct kernel_lb_addr *eloc, uint32_t *elen, int inc)
{
int alen;
int8_t etype;
uint8_t *ptr;
struct short_ad *sad;
struct long_ad *lad;
struct udf_inode_info *iinfo = UDF_I(inode);
if (!epos->bh) {
if (!epos->offset)
epos->offse... | 268,227,664,792,364,700,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,900 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | int8_t udf_delete_aext(struct inode *inode, struct extent_position epos,
struct kernel_lb_addr eloc, uint32_t elen)
{
struct extent_position oepos;
int adsize;
int8_t etype;
struct allocExtDesc *aed;
struct udf_inode_info *iinfo;
if (epos.bh) {
get_bh(epos.bh);
get_bh(epos.bh);
}
iinfo = UDF_I(in... | 192,357,336,692,058,300,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,901 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static ssize_t udf_direct_IO(int rw, struct kiocb *iocb,
struct iov_iter *iter,
loff_t offset)
{
struct file *file = iocb->ki_filp;
struct address_space *mapping = file->f_mapping;
struct inode *inode = mapping->host;
size_t count = iov_iter_count(iter);
ssize_t ret;
ret = blockdev_direct_IO(rw, ... | 42,707,201,640,901,850,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,902 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | struct buffer_head *udf_expand_dir_adinicb(struct inode *inode, int *block,
int *err)
{
int newblock;
struct buffer_head *dbh = NULL;
struct kernel_lb_addr eloc;
uint8_t alloctype;
struct extent_position epos;
struct udf_fileident_bh sfibh, dfibh;
loff_t f_pos = udf_ext0_offset(inode);
int size = udf_e... | 307,405,161,000,093,050,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,903 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | int udf_expand_file_adinicb(struct inode *inode)
{
struct page *page;
char *kaddr;
struct udf_inode_info *iinfo = UDF_I(inode);
int err;
struct writeback_control udf_wbc = {
.sync_mode = WB_SYNC_NONE,
.nr_to_write = 1,
};
WARN_ON_ONCE(!mutex_is_locked(&inode->i_mutex));
if (!iinfo->i_lenAlloc) {
if (UDF_... | 118,888,461,631,358,180,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,904 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static int udf_extend_file(struct inode *inode, loff_t newsize)
{
struct extent_position epos;
struct kernel_lb_addr eloc;
uint32_t elen;
int8_t etype;
struct super_block *sb = inode->i_sb;
sector_t first_block = newsize >> sb->s_blocksize_bits, offset;
int adsize;
struct udf_inode_info *iinfo = UDF_I(inode);
... | 277,479,830,577,478,460,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,905 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static int udf_get_block(struct inode *inode, sector_t block,
struct buffer_head *bh_result, int create)
{
int err, new;
sector_t phys = 0;
struct udf_inode_info *iinfo;
if (!create) {
phys = udf_block_map(inode, block);
if (phys)
map_bh(bh_result, inode->i_sb, phys);
return 0;
}
err = -EIO;
new =... | 112,485,993,264,854,330,000,000,000,000,000,000,000 | inode.c | 299,509,065,903,875,730,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,906 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static struct buffer_head *udf_getblk(struct inode *inode, long block,
int create, int *err)
{
struct buffer_head *bh;
struct buffer_head dummy;
dummy.b_state = 0;
dummy.b_blocknr = -1000;
*err = udf_get_block(inode, block, &dummy, create);
if (!*err && buffer_mapped(&dummy)) {
bh = sb_getblk(inode->... | 288,797,577,807,295,200,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,907 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | struct inode *udf_iget(struct super_block *sb, struct kernel_lb_addr *ino)
{
unsigned long block = udf_get_lb_pblock(sb, ino, 0);
struct inode *inode = iget_locked(sb, block);
if (!inode)
return NULL;
if (inode->i_state & I_NEW) {
memcpy(&UDF_I(inode)->i_location, ino, sizeof(struct kernel_lb_addr));
__udf_... | 208,414,677,112,964,700,000,000,000,000,000,000,000 | inode.c | 233,698,405,973,444,620,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,908 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static int8_t udf_insert_aext(struct inode *inode, struct extent_position epos,
struct kernel_lb_addr neloc, uint32_t nelen)
{
struct kernel_lb_addr oeloc;
uint32_t oelen;
int8_t etype;
if (epos.bh)
get_bh(epos.bh);
while ((etype = udf_next_aext(inode, &epos, &oeloc, &oelen, 0)) != -1) {
udf_write_a... | 103,836,132,997,594,870,000,000,000,000,000,000,000 | inode.c | 299,509,065,903,875,730,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,909 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static void udf_merge_extents(struct inode *inode,
struct kernel_long_ad laarr[EXTENT_MERGE_SIZE],
int *endnum)
{
int i;
unsigned long blocksize = inode->i_sb->s_blocksize;
unsigned char blocksize_bits = inode->i_sb->s_blocksize_bits;
for (i = 0; i < (*endnum - 1); i++) {
struct kernel_long_ad ... | 111,658,090,834,935,210,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,910 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | int8_t udf_next_aext(struct inode *inode, struct extent_position *epos,
struct kernel_lb_addr *eloc, uint32_t *elen, int inc)
{
int8_t etype;
while ((etype = udf_current_aext(inode, epos, eloc, elen, inc)) ==
(EXT_NEXT_EXTENT_ALLOCDECS >> 30)) {
int block;
epos->block = *eloc;
epos->offset = siz... | 173,180,639,176,931,500,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,911 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static void udf_prealloc_extents(struct inode *inode, int c, int lastblock,
struct kernel_long_ad laarr[EXTENT_MERGE_SIZE],
int *endnum)
{
int start, length = 0, currlength = 0, i;
if (*endnum >= (c + 1)) {
if (!lastblock)
return;
else
start = c;
} else {
if ((laarr[c + 1].extLength >> 30) ==
... | 123,142,960,587,158,420,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,912 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static int udf_read_extent_cache(struct inode *inode, loff_t bcount,
loff_t *lbcount, struct extent_position *pos)
{
struct udf_inode_info *iinfo = UDF_I(inode);
int ret = 0;
spin_lock(&iinfo->i_extent_cache_lock);
if ((iinfo->cached_extent.lstart <= bcount) &&
(iinfo->cached_extent.lstart != -1)) {
/*... | 58,614,091,322,101,480,000,000,000,000,000,000,000 | inode.c | 299,509,065,903,875,730,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,913 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static int udf_readpage(struct file *file, struct page *page)
{
return mpage_readpage(page, udf_get_block);
}
| 214,263,694,444,569,460,000,000,000,000,000,000,000 | inode.c | 299,509,065,903,875,730,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,914 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static int udf_readpages(struct file *file, struct address_space *mapping,
struct list_head *pages, unsigned nr_pages)
{
return mpage_readpages(mapping, pages, nr_pages, udf_get_block);
}
| 187,464,471,445,705,440,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,915 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | int udf_setsize(struct inode *inode, loff_t newsize)
{
int err;
struct udf_inode_info *iinfo;
int bsize = 1 << inode->i_blkbits;
if (!(S_ISREG(inode->i_mode) || S_ISDIR(inode->i_mode) ||
S_ISLNK(inode->i_mode)))
return -EINVAL;
if (IS_APPEND(inode) || IS_IMMUTABLE(inode))
return -EPERM;
iinfo = UDF_I... | 25,579,638,656,999,810,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,916 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static void udf_split_extents(struct inode *inode, int *c, int offset,
int newblocknum,
struct kernel_long_ad laarr[EXTENT_MERGE_SIZE],
int *endnum)
{
unsigned long blocksize = inode->i_sb->s_blocksize;
unsigned char blocksize_bits = inode->i_sb->s_blocksize_bits;
if ((laarr[*c].extLength... | 268,391,852,871,414,500,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,917 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static int udf_sync_inode(struct inode *inode)
{
return udf_update_inode(inode, 1);
}
| 270,119,703,924,943,400,000,000,000,000,000,000,000 | inode.c | 299,509,065,903,875,730,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,918 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static void udf_update_extents(struct inode *inode,
struct kernel_long_ad laarr[EXTENT_MERGE_SIZE],
int startnum, int endnum,
struct extent_position *epos)
{
int start = 0, i;
struct kernel_lb_addr tmploc;
uint32_t tmplen;
if (startnum > endnum) {
for (i = 0; i < (startnum - endnum)... | 34,885,046,154,244,600,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,919 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static int udf_update_inode(struct inode *inode, int do_sync)
{
struct buffer_head *bh = NULL;
struct fileEntry *fe;
struct extendedFileEntry *efe;
uint64_t lb_recorded;
uint32_t udfperms;
uint16_t icbflags;
uint16_t crclen;
int err = 0;
struct udf_sb_info *sbi = UDF_SB(inode->i_sb);
unsigned char blocksize_b... | 308,832,633,212,933,700,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,920 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | void udf_write_aext(struct inode *inode, struct extent_position *epos,
struct kernel_lb_addr *eloc, uint32_t elen, int inc)
{
int adsize;
uint8_t *ptr;
struct short_ad *sad;
struct long_ad *lad;
struct udf_inode_info *iinfo = UDF_I(inode);
if (!epos->bh)
ptr = iinfo->i_ext.i_data + epos->offset -
udf_... | 150,846,098,624,912,270,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,921 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static int udf_write_begin(struct file *file, struct address_space *mapping,
loff_t pos, unsigned len, unsigned flags,
struct page **pagep, void **fsdata)
{
int ret;
ret = block_write_begin(mapping, pos, len, flags, pagep, udf_get_block);
if (unlikely(ret))
udf_write_failed(mapping, pos + len);
return ret;... | 140,233,577,978,068,230,000,000,000,000,000,000,000 | inode.c | 299,509,065,903,875,730,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,922 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static void udf_write_failed(struct address_space *mapping, loff_t to)
{
struct inode *inode = mapping->host;
struct udf_inode_info *iinfo = UDF_I(inode);
loff_t isize = inode->i_size;
if (to > isize) {
truncate_pagecache(inode, isize);
if (iinfo->i_alloc_type != ICBTAG_FLAG_AD_IN_ICB) {
down_write(&iinfo->... | 327,906,769,285,573,100,000,000,000,000,000,000,000 | inode.c | 299,509,065,903,875,730,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,923 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | int udf_write_inode(struct inode *inode, struct writeback_control *wbc)
{
return udf_update_inode(inode, wbc->sync_mode == WB_SYNC_ALL);
}
| 264,157,910,409,832,900,000,000,000,000,000,000,000 | inode.c | 299,509,065,903,875,730,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
36,924 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static int udf_writepages(struct address_space *mapping,
struct writeback_control *wbc)
{
return mpage_writepages(mapping, wbc, udf_get_block);
}
| 92,572,591,415,466,260,000,000,000,000,000,000,000 | inode.c | 299,509,065,903,875,730,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.